Suggest topics for the July 1, 2010 dev …

Welcome!

The WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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 bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.? Create a ticket in the bug tracker.
Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.
Other questions? Here is a detailed handbook for contributors, complete with tutorials.

Jane Wells 4:01 pm on June 25, 2010

3.org dev team assignments/accepted projects.
filosofo 4:21 pm on June 25, 2010

Let’s please set a specific date for when 3.1 development resumes.

The longer it remains indefinite the more likely it will discourage participation from newcomers and casual contributors.
Rafael Poveda - RaveN 4:38 pm on June 25, 2010

Here I think Sept the 1st is a good date to resume trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. work. Casual contributors will do as usual: will put their tickets in tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. and, if they are blockers, will be in next minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. ASAP. If they want to see their changes sooner, they can use nightly build if their patches are committed.

I don’t think newcomers will have problems with this if they know that we are working in a better and more complete .org for a while.

Also, 9/1 is the ‘back to work’ date for most companies. It’s like we are using summertime to work in other things. We can assume that in July we aren’t going to work much in trunk after all the sprint work done, and we also need this month to move all our client/customers systems to 3.0. Companies like mine have a lot of custom personalization done for clients and we need some time to move them to 3.0. And August is holidays month for most people.

I think we have more pros than cons with this pause time.
hakre 5:44 pm on June 26, 2010

This weeks dev chat results are still not published. Wasn’t it promised that this will be done after last meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area.?
- Andrew Nacin 6:00 pm on June 26, 2010
  
  We don’t always get around to writing a summary. The hiatus post rather accurately describes what we’re going with. There are also logs. And, you were there, so I’m not sure why you need a summary.
hakre 9:39 pm on June 27, 2010

Well I just thought this is helpful to have with these grave changes. No need to be offended again Nacin, I’m too lazy to look it up in the logs but somebody (I’m pretty sure that wasn’t you) said, there will be a summary. So I was just asking for it.

Comments are closed.

Welcome!

Communication

Share this:

Site resources