Release candidate and today’s dev meeting agenda

Welcome!

The WordPress core development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:

Found a bug? Create a ticket in our bug tracker.
Want to contribute? Get started quickly with our tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on our reports page, like patches needing testing.
Other questions? We also have a detailed handbook for contributors, complete with tutorials.

#4-1, #agenda

4.1 was originally due for release today, but a few tickets in the 4.1 milestone have held things up a little. The release candidate will be tagged in time for today’s dev meeting at December 10 2014 21:00 UTC, and the target release date is now ~~Monday, December 15th~~ Tuesday December 16th.

Here’s the agenda for today’s dev meeting:

Documentation from various make/core posts need to go into the plugin handbook and theme handbook.
The 4.1 page on the Codex is in progress.
Eyes on the support forums – the alpha/beta forum has seen almost no activity so we need eyes on the forums as a whole.
‘About’ page design – @melchoyce, kelly, @helen #30435
Plugin developers – update your plugin’s readme files to indicate support for 4.1 once RC1 is released. You’ve tested all your plugins with the beta, yeah?
Looking for something to do? Tickets reported against trunk needs some continued triaging.
Status of plugin directory l10n and recommended plugins tab. @stephdau @tellyworth
Discuss status of l10ns for polyglots.
Discuss a status update meeting type thing on Sunday.
Discuss release plan. @nacin
Any other business.

#4-1, #agenda

Jeff Chandler 7:26 pm on December 10, 2014

One possible reason for the Alpha/Beta forums having low activity is that there hasn’t been much in the way of beta release communication on the WordPress.org development blog. There’s a small mention of a beta at the bottom of the 4.0.1 security update post but that’s from Late November. Hopefully, news of the RC1 release will be published on the official blog and that might get things going again on those forums.

In that post, I’d also like to see specific items you want people to test.
- John Blackbourn 8:55 pm on December 10, 2014
  
  Yeah we usually do separate posts for each beta but we got a bit caught up with 4.0.1 landing at the same time.
Stephane Daury (stephdau) 8:39 pm on December 10, 2014
Plugin Directory l10n

I’ve just uploaded a major milestone to #760-meta which bring the complete solution to life, as what I’d qualify as a sophisticated proof-of-concept (as in still needs a lot of work/testing but shows everything off):
- code & readme translation processing
- localized directories content translation display (wporg code already use gettext for its strings, that’s covered)
- translation caching policy, as well cache expunging on interaction with translate.wordpress.org (imports, edits, etc)
- api content translation display when passed a language param (arbitrary, not set-in-stone)
See screenshots showing it in action here: https://cloudup.com/cmAHT9qu2Wx
Lance Willett 8:56 pm on December 10, 2014

For release plan, I’ll be on duty to prepare new versions of default themes for submission to Themes directory.
Michel - xiligroup dev 12:48 pm on December 11, 2014

@john
Just a question of release : why when, testing feature on a temporary website, updating from admin from 4.1beta2 …734, we arrive directly to 4.2 alpha… and with no RC release…
Please tell how to fin RC nighty build
conservativeread 1:06 pm on December 11, 2014

same issue here updating from admin from 4.1beta2 we arrive directly to 4.2 alpha
Xavier Borderie 2:03 pm on December 11, 2014

@michelwppi @conservativeread As discussed on Slack, “[the developers] branched 4.1 a bit earlier this time, that’s why you’re getting 4.2-alpha. The plugin gives you the nightly build from trunk, not the branch.”
Michel - xiligroup dev 4:18 pm on December 11, 2014

@[the developers]
Branching is practical for developers… but not for ‘devoted’ testers… the update page in WP dashboard is unusable with / for RC versions… So need to use again FTP client even on localhost… and avoid again to go to 4.2 alpha… I am sure that developers can solve the UX issue 😉
- Knut Sparhell 5:09 pm on December 11, 2014
  
  I second this. I was really annoyed by experiencing the beta tester plugin took me to 4.2.alpha insted of 4.1-RC1. If you (leads) are going to branch out before last RC in the future please give us a beta tester with three options (point releases, beta/RC or trunk). Those who always want latest alphas select trunk, betaRC-testers select beta/RC. During the cycle we can change option from trun to btea/RC to avoid this, and still have alphas at the start of a cycle.

Comments are closed.

WordPress.org

Welcome!

Communication

Share this: