This is the official blog for the core development team of the WordPress open source project. Follow our progress with weekly meeting agendas, project schedules, and the occasional code debate.
Can we keep ticket discussion to trac unless it really needs discussion in the meetup so we don’t end up filling the agenda with things which have already been resolved.
Imo, we should really fix this. Even if it means breaking a few plugins on the way. the various option, transient, and meta functions should all expect the setting’s name and value to be unslashed.
Google Summer of Code. Potential mentors, potential projects. I’ll be submitting the WordPress application for participation in a week, will need to ID that stuff.
I thought if sites in the 2.9/2.8 trunk can test it as well it would gain more attention, that’s all. If it actually is not working with those like Westi writes – or not even intended – then this advantage in testing is not available, true.
In case 3.0 is not finished as quick as expected (I do not mean the number of the year), this might prevent 2.x backports of the theme. Just an Idea.
I would agree here 2010 is designed to be a 3.0 theme and makes use of 3.0 features.
I’m not sure what end-user benefit there is in making it 2.9.x compatible – it leverages a lot of new core features to provide a good UX.so you would need to backport all of those too!
Given the growth in multi-site related tickets at the tail end of the patch sprint, we should discuss whether sprints should be undertaken in the future. And, if so, should the sprint be managed by one of the leads instead of a junior commiter.
I’m not sure I’ve seen a growth of MS tickets, aside from those that Denis has been submitting for all major features over the last few days. Clearing out the enhancement tickets didn’t cause more merge bugs. And while I spent a good amount of time triaging those tickets and massaging the report, I wasn’t under the assumption I was managing anything. (I assume you’re talking about me ).
Regarding Multisite, there are a few outstanding high priority tickets, both of which are marked as blockers. The first would be the bug related to i18n and hard-coded strings in http://core.trac.wordpress.org/ticket/12357, which if no one tackles, I will, but it would be nice if someone can work on that. The second is the Tools > Network overhaul with WP_Filesystem (http://core.trac.wordpress.org/ticket/12094). I circled back to the latter ticket over the weekend and I’ve enlisted Dion to ensure we can make quick progress in the next few days so more people can begin to kick the MS tires. (There’s also a starter patch waiting there for review.)
Thanks for getting that wpfs in I will give it a run tonight or tomorrow. I did the i18n this morning. So that is also looked after.
I was expecting that there was going to be a specific test/pre-beta build put up for download and that the build was waiting for those tickets I marked. I talked to Ryan in IRC and he clarified how the freeze to beta was being done. Sorry for the priority elevation, etc. in the comments.
I have a dentist appointment on Thursday afternoon. I probably will miss the the first half of the meetup.
Another alternative we might consider is a 24 (or 48) hour test period prior to the freeze.
Denis de Bernardy 1:11 am on February 27, 2010 Permalink |
http://core.trac.wordpress.org/ticket/12400
Peter Westwood 9:48 pm on March 1, 2010 Permalink |
Looks like this is already committed.
Can we keep ticket discussion to trac unless it really needs discussion in the meetup so we don’t end up filling the agenda with things which have already been resolved.
Denis de Bernardy 2:47 am on February 27, 2010 Permalink |
This one too, if it hasn’t been checked in by then:
http://core.trac.wordpress.org/ticket/12402
Denis de Bernardy 1:42 am on February 28, 2010 Permalink |
Imo, we should really fix this. Even if it means breaking a few plugins on the way. the various option, transient, and meta functions should all expect the setting’s name and value to be unslashed.
http://core.trac.wordpress.org/ticket/12416
Peter Westwood 9:50 pm on March 1, 2010 Permalink |
Looks like this is already being worked on too.
Jane Wells 9:05 am on February 28, 2010 Permalink |
Google Summer of Code. Potential mentors, potential projects. I’ll be submitting the WordPress application for participation in a week, will need to ID that stuff.
Jeffro 9:30 pm on February 28, 2010 Permalink |
It’s that time of year again already? Wow.
hakre 12:36 pm on March 1, 2010 Permalink |
I suggest an update on 2010 with a focus on 2010 backwards compability to 2.8.x / 2.9.x.
Alex M. 12:44 pm on March 1, 2010 Permalink |
What would be the advantage of this? We want to encourage people to upgrade their version of WordPress, not the reverse.
hakre 8:01 pm on March 2, 2010 Permalink
I thought if sites in the 2.9/2.8 trunk can test it as well it would gain more attention, that’s all. If it actually is not working with those like Westi writes – or not even intended – then this advantage in testing is not available, true.
In case 3.0 is not finished as quick as expected (I do not mean the number of the year), this might prevent 2.x backports of the theme. Just an Idea.
Jane Wells 10:20 am on March 4, 2010 Permalink
I agree that 2010 is not intended for use on pre-3.0 versions. We will be doing a new theme each year from now on. We will not backdate the theme.
Peter Westwood 9:51 pm on March 1, 2010 Permalink |
I would agree here 2010 is designed to be a 3.0 theme and makes use of 3.0 features.
I’m not sure what end-user benefit there is in making it 2.9.x compatible – it leverages a lot of new core features to provide a good UX.so you would need to backport all of those too!
wpmuguru 9:34 pm on March 2, 2010 Permalink |
Given the growth in multi-site related tickets at the tail end of the patch sprint, we should discuss whether sprints should be undertaken in the future. And, if so, should the sprint be managed by one of the leads instead of a junior commiter.
Andrew Nacin 11:21 pm on March 2, 2010 Permalink |
I’m not sure I’ve seen a growth of MS tickets, aside from those that Denis has been submitting for all major features over the last few days. Clearing out the enhancement tickets didn’t cause more merge bugs. And while I spent a good amount of time triaging those tickets and massaging the report, I wasn’t under the assumption I was managing anything. (I assume you’re talking about me
).
Regarding Multisite, there are a few outstanding high priority tickets, both of which are marked as blockers. The first would be the bug related to i18n and hard-coded strings in http://core.trac.wordpress.org/ticket/12357, which if no one tackles, I will, but it would be nice if someone can work on that. The second is the Tools > Network overhaul with WP_Filesystem (http://core.trac.wordpress.org/ticket/12094). I circled back to the latter ticket over the weekend and I’ve enlisted Dion to ensure we can make quick progress in the next few days so more people can begin to kick the MS tires. (There’s also a starter patch waiting there for review.)
Ron 6:02 pm on March 3, 2010 Permalink
Thanks for getting that wpfs in
I will give it a run tonight or tomorrow. I did the i18n this morning. So that is also looked after.
I was expecting that there was going to be a specific test/pre-beta build put up for download and that the build was waiting for those tickets I marked. I talked to Ryan in IRC and he clarified how the freeze to beta was being done. Sorry for the priority elevation, etc. in the comments.
Andrew Nacin 6:50 pm on March 3, 2010 Permalink
No wpfs yet, just groundwork for it. Coming soon though… And no problem
wpmuguru 11:25 pm on March 2, 2010 Permalink |
I have a dentist appointment on Thursday afternoon. I probably will miss the the first half of the meetup.
Another alternative we might consider is a 24 (or 48) hour test period prior to the freeze.
Ron 5:54 pm on March 3, 2010 Permalink |
From my perspective, this can be removed from the agenda. We made feature freeze yesterday.
Denis de Bernardy 12:34 pm on March 3, 2010 Permalink |
MS uploads, in the lights of #11742 and #12496.
Nikolay Bachiyski 10:14 am on March 4, 2010 Permalink |
I18n-or-not of 2010
Xavier 2:55 pm on March 4, 2010 Permalink |
Also, why the strings for 2010 are in the general POT, and not in a separate one as it was for Kubrick?
demetris 8:05 pm on March 4, 2010 Permalink |
I wrote down some thoughts on the i18n of Twenty Ten and of WP 3.0: http://docs.google.com/View?id=dd78mj55_42fppqgsck
The text was too long to post here as a comment, but, in essence, it is just a couple of ideas.
Cheers!