Since in the last dev chat we agreed to take the holidays off and come back in January and determine the scope for 3.0, I’d like to suggest that people stop changing ticket milestones to 3.0 for now, so that we can reduce the amount of Trac rehashing we have to do after we set the scope in the first dev meeting back. Also, we may want to plan on that first meeting being longer than the usual hour.
Recent comments
siobhyb on JSON REST API siobhyb on OPW Introduction – Hello… Dan on JSON REST API tuyendart on JSON REST API Tips Tuesday – Relea… on Summer of Code Revisions
Jane Wells 9:56 pm on December 23, 2009 Permalink
There are already 320 tickets against the 3.0 milestone without even thinking about the merge, so if anyone is antsy to work on stuff for 3.0, those tickets are probably a better place to start than something that got punted to future release instead of 3.0.
Shane 2:52 pm on December 24, 2009 Permalink
Maybe the 3.1.0 milestone should be created and the tickets/features that are not as big as lets say:
*WPMY
*Media Overhaul – This should be done at the same time since there will be lots of code changing and what not.
I would even maybe move my widgets API idea off till 3.1, but if put in 3.0 the long dev cycle should help with the transition with most widget authors if we adopt the idea.
I am thinking we need at least 2 hours to discuss the huge changes for the 3.x milestone.
Merge news and Buddypress awesomeness - WPMU Tutorials 6:37 pm on December 27, 2009 Permalink
[...] are also the weekly dev chats, except the next one has a bit of holiday break. If you want to have a say, or just read along in [...]