Let’s have a meeting today, Tuesday April 15, 2014, 18:00 UTC, to make sure we have everything in place for a release. (#wordpress-dev)
Tagged: agenda Toggle Comment Threads | Keyboard Shortcuts
Please suggest items for the April 2 developer meeting. So far:
As a reminder, the weekly meeting continues to be at 21:00 UTC.
Daylight Saving Time has started in the U.S., which means the meeting is at 5 p.m. Eastern time, 2 p.m. Pacific. We will revert to 20:00 UTC on April 2, after Europe enters Daylight Saving Time.
Our agenda for today will be to go over all 3.9 tasks and get an idea where we need the most resources, to ensure we are in a good position to close out the beta period in less than three weeks.
Please suggest agenda items for the February 12 developer meeting.
Aside from usual 3.9 stuff, we’re going to be using part of this meeting for brainstorming for GSoC.
Please suggest agenda items for the weekly developer meeting, Wednesday, February 5, 21:00 UTC.
If there’s a task or ticket we need to work through, or need volunteers for, let’s get those spelled out now. Maybe we can even work through some of them pre-meeting.
I’ll again be asking for a sentence or two (or more, if necessary of course) from each person/team working on a 3.9 task. You can also post those here if you’d like — please cross-reference any relevant tickets or discussions. Worked out great last week. For the state of things as of last week, see Mike’s weekly roundup.
Please propose agenda items for the development meeting today at 21:00 UTC. Let’s try to keep it to under an hour, like last week’s.
Some to start us off:
- Consider the Widgets Customizer plugin for 3.9 merge. If you haven’t looked at it yet, please spend some time today before the meeting. Obviously, we all like the idea, but we need to study the implementation and provide feedback. Please comment on that post if you haven’t already.
- I’d like to propose an initiative for cleaning up a group of 556 tickets during the 3.9 cycle. (It has details, will explain in the meeting.)
- Quick situation reports for various 3.9 tasks. If you’re working on something, please come armed with a sentence so we can do these rapid-fire — or post it in the comments thread. Some things are moving forward quickly, some aren’t. Where can we help? Here’s a list of what was proposed for 3.9 (see also the comments, which were updated after the last meeting). We need to take the “proposed” label off soon…
- I’d like to get moving on the Trac component re-organization; I’ll see if there are any questions. We will need some help to move around tickets (ideally adding feedback to them along the way), so I’ll be looking for volunteers and talking about what is needed.
Aren’t familiar with how these meetings work? They’re especially good for breaking logjams — whether that means talking through a major sticking point, finding volunteers to help with something. We also use them to plan out schedules and tasks, make sure everyone is on the same page, and do release post-mortems to see how things went. (As 3.8.1 was released on Thursday, could be good to discuss this and 3.8.2, for example.)
The meeting takes place in IRC on chat.freenode.net in the #wordpress-dev channel. See you then!
Proposed agenda for today’s dev chat (~35 minutes from now):
- Initial debrief for 3.8. Start to think about what we can learn from 3.8.
- Status report of bugs/regressions for 3.8.1. Look at a tentative 3.8.1 timeline.
- Initial 3.9 discussion. Discuss potential feature plugin candidates, timeline, and release leads.
@matt will be running a WordPress 3.8 feature planning/decisions meeting on Monday, November 4, 21:00 UTC. Now that Daylight Saving Time has ended for both Europe and the U.S., note that the weekly Wednesday meeting is now moved from 20:00 UTC to 21:00 UTC (4 p.m. EST, 1 p.m. PST). (Americans, change your clocks on Sunday.)
I’d strongly encourage everyone to study, test, and weigh in on the four 3.8 proposals before the meeting. I believe the goal of the meeting will be to establish what exactly gets merged into 3.8.
API enhancements, bug fixes, etc. can/will continue as usual — it would be awesome if we had a surge not unlike 3.7. But for now, 3.7.1 is out, so stare at the download counter sip some tea, and relax this the weekend.
Agenda for today’s meeting in #wordpress-dev at 20:00 UTC.
- Go over the last few days of progress, as well as what we’ve been learning via statistics for background updates. (Spoiler: excellent.)
- Need a commit or revert on #20316 (garbage collect transients). It has a patch — the queries need testing and review.
- Need a decision on #24963 (IIS stuff).
- Finalize the about page. It’s going to be text-heavy as there’s nothing to show off UI-wise. What about a single giant three-column image across the top? I mean, it can be a picture of a sunrise for all I care. Or some screenshot of the WordPress admin. Or some photos from the crowds at WordCamp San Francisco and WordCamp Europe. Anyone have any ideas?
- WordPress 3.7 Release Candidate 1 (by tonight).
- Branch WordPress 3.7 (after RC1).
For the meeting today (starts in ~20 minutes), we need to work on getting to 3.7 Beta 1. I think if all goes well, we can release Beta 1 tonight or tomorrow morning. @dd32 has been doing some incredible work on automatic updates. If you haven’t read his post on them, please do!
So, there are a few things we need to discuss and make decisions on:
1. Search results ordered by relevance, #7394. Do we take a chance on this?
2. Should we begin to require that users supply their current password in order to change their password? #20140.
3. Should we consider a slightly more conservative different approach to transient garbage collection? We do not want updates to be blamed for breaking sites. #20316. What would this approach look like?
4. How should individuals be notified via email when it comes to automatic background updates? #10787.
5. How should individuals be notified their own dashboard that their site will be safe if there is a security release?
Proposal for points 4 and 5: A green checkmark on about.php and update-core.php will let them know their install is OK and good to go for automatic background updates for security releases. (We can easily verify this without prompting the user.)
If for some reason we attempt an automatic background update and it fails to complete, then we need to email
get_site_option( 'admin_email' ). We need text for this email.
If they don’t have a green checkmark, we should wait five days, after which we email them reminding them a security release is available. A timestamp five days from the point of release will be pushed via the API. Once that time is crossed, an email will be sent. (For a particularly critical situation, we could shorten the timeframe. For a non-security minor release, we might avoid having an email sent all together). We also need text for this email (which will be a fairly nice email).
This does not accomplish all of #10787 (“Email administrators that an update is available for core, plugins, and themes”) but it seems to be a good security balance.
My target is Beta 2 early next week, and Release Candidate 1 as early as next Friday. Here is our current progress on tickets:
- There are no more enhancements or feature requests open on the 3.7 milestone.
- There are under 20 tasks remaining for 3.7. Many of these are near completion. These need to be cleared by Beta 2.
- There are 150 bugs open on the 3.7 milestone. We need to reduce this number to about 75 by Friday, and to zero by the end of next week. As in, these need to be cleared by RC1.
We’ll likely branch 3.7 at the WordCamp Europe contributor day on October 7, which means anything that is punted out of 3.7 can still make it into 3.8 starting in just two short weeks from now. A reminder, this is a very short release cycle, and 3.8 is just a few months away and begins in earnest very soon. Here is what our philosophies document says about fast, agile release cycles with crisp deadlines:
The more frequent and regular releases are, the less important it is for any particular feature to be in this release. If it doesn’t make it for this one, it’ll just be a few months before the next one. When releases become unpredictable or few and far between, there’s more pressure to try and squeeze in that one more thing because it’s going to be so long before the next one. Delay begets delay.
If we’re not confident that three weeks is long enough for something to properly soak in trunk, let’s not be afraid to wait until 3.8.
Mattias Tengblad, Shapeshifter 3, WordPress › Support Team Update for September 26th 2013 « Make.WordPress.Org Updates, and 1 other are discussing. Toggle Comments