Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #38672, comment 5


Ignore:
Timestamp:
11/04/2016 09:51:08 PM (8 years ago)
Author:
helen
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #38672, comment 5

    initial v1  
    55Since we don't really have interface collisions here, I ''think'' the technical difference may really boil down to the name of the CPT and whether you start a new post for each theme with its own revisions (as core is doing) or you use one post with revisions forever with the theme info stored for each revision (as Jetpack appears to be doing).
    66
    7 Core can change what it's doing fairly easily because we're in beta, but I want to make sure we are working with the Jetpack team just as we should work with anybody behind a plugin with major adoption whose features match something that is coming into core. I really hope this was an honest oversight and not a case of not-invented-here, "ugh Automattic" syndrome, because this is an incredibly annoying thing for myself and many others coming awfully late in the development cycle. There is a serious risk of dropping this from 4.7 because of this.
     7Core can change what it's doing fairly easily because we're in beta, but I want to make sure we are working with the Jetpack team just as we should work with anybody behind a plugin with major adoption whose features match something that is coming into core. I really hope this was an honest oversight and not a case of not-invented-here, "ugh Automattic" syndrome, because this is an incredibly annoying thing for myself and many others coming awfully late in the development cycle. There is a serious risk of dropping this feature from 4.7 because of this.