We migrated all the .org trac installs a…

We migrated all the .org tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. installs and svn repositories (except WP.org plugins which had been moved previously) to a new server today and upgraded from Trac 0.11 to 0.12. Unfortunately, it didn’t go so well and trac is somewhat broken (sporadic internal errors, custom queries not working, reports showing wrong data). SVNSVN Subversion, the popular version control system (VCS) by the Apache project, used by WordPress to manage changes to its codebase. is working fine. We are working on figuring out the problem and will update this post once we have more information. Sorry for the trouble.

#trac

I’ve emptied and deleted the Awaiting T…

I’ve emptied and deleted the Awaiting Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. milestone. This milestone had held 3.1 tickets before we decided to empty that bucket out and start again.

We still have nearly 500 tickets in Awaiting Review. We should try to whittle those down before betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. hits and that gets flooded.

#trac

I have had InterTrac linking enabled fro…

I have had InterTrac linking enabled from the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. to a few others and back the other way (previously the core trac had a minimal configuration).

You can now refer to changesets and tickets in related tracs as follows:

Dropped the Awaiting Review queue by abo…

Dropped the Awaiting Review queue by about 150 tickets in the last two evenings. There’s another 450 there, and 290 in Awaiting Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors.. You may recall that Awaiting Triage were 3.1 tickets prior to us rebooting that milestone. Ideally Triage should be emptied.

Hoping to reduce both significantly before betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. goes out and we get flooded, so I’m going to aim to handle about 50 a night.

Feel free to jump in at any point. 🙂

#trac

Due to some spam, I just disabled commen…

Due to some spam, I just disabled commenting permissions for regular users on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., and took other measures which I’ll relay to Barry and the rest of the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team. Will post here with an update soon.

#spam, #trac

WordPress 3.0.1 is released. 55 tickets …

WordPress 3.0.1 is released. 55 tickets went into it. I opened the 3.0.2 milestone last week, and just now I’ve closed 3.0.1.

We pushed 3.0.1 twice, the second time about 20 minutes later, as we forgot about #14454. Not a big deal, but we’ve recommended over Twitter and on the announcement that you update again if you downloaded it before 2200 UTC.

We did a db version bump with the hope that we could force the APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. to return 3.0.1 again if you’re not at the proper version, but we don’t pass the db version via wp_update_check(). (@todo).

#releases, #trac

The Unassigned milestone has been rename…

The Unassigned milestone has been renamed to Awaiting Review. (If TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. gives you any “Invalidinvalid A resolution on the bug tracker (and generally common in software development, sometimes also notabug) that indicates the ticket is not a bug, is a support request, or is generally invalid. Milestone Name” errors, just refresh.)

Additionally, all open tickets in the 3.1 milestone have been moved to a temporary Awaiting Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. milestone, to enable us to re-sort these without mixing these in with new tickets coming in, to ensure new tickets are reviewed as soon as possible after submission.

Per our timeline, 3.1 now says active development will begin in September 2010.

#trac

Agenda for June 24 developer chat. – Rev…

Agenda for June 24 developer chat.

  • Review of 3.0 feedback – incoming ticketticket Created for both bug reports and feature development on the bug tracker. rate, common issues, etc. – All
  • TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. Changes – Nacin/Mark
  • Next steps: 3.org and 3.1 – All

#3-org, #agenda, #trac

The ability to set “priority” and “mi…

The ability to set “priority” and “milestone” for WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets has been restricted. Unknown Trac users will not be able to set them when creating or updating tickets. These fields were being somewhat misused by casual Trac users — e.g. setting priority higher than it should be, or sticking things in the 3.0 milestone when 3.0 was in RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta).. We are adding the ability to set these fields to known WP contributors based on frequency and quality of code and ticketticket Created for both bug reports and feature development on the bug tracker. contributions. That list is not complete, so don’t micro-analyze the inclusion or non-inclusion of anyone at this point! 🙂

This should help WordPress avoid having hundreds of tickets on a milestone that need to be punted in the weeks before release. We can be more judicious in assigning a milestone to a ticket.

#trac

I marked the 2.9.3 milestone as “comple…

I marked the 2.9.3 milestone as “completed” on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., even though it never shipped, I removed the 2.9.3 milestone on Trac and shifted those tickets to 3.0, which means the 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. reports now reflect 3.0.1.

That milestone is for “security and blockerblocker A bug which is so severe that it blocks a release.-level bugs” only. That doesn’t mean all other tickets belong in 3.1, though. I’m going to suggest tickets are triaged in the following fashion:

  • Anything in the 3.1 milestone that is not owned by a committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. or seriously deserving of 3.1 consideration will be moved to future release (prior to our scope meeting) to keep 3.1 clear of debris. After a scope meeting, we can selectively pull tickets into 3.1 as we go. (Currently 340 tickets are marked for 3.1.)
  • The Unassigned milestone should be emptied, sans reporter-feedback-like tickets that we can’t place into a milestone yet. All new tickets should start here. (There are currently 169 tickets without a milestone.)
  • The Future Release milestone needs a good drudging for it to become truly useful again, as there are probably hundreds of tickets there that can be closed as duplicate, invalidinvalid A resolution on the bug tracker (and generally common in software development, sometimes also notabug) that indicates the ticket is not a bug, is a support request, or is generally invalid., worksformeworksforme A resolution on the bug tracker (and generally common in software development) that indicates the bug reported cannot be reproduced., or wontfixwontfix A resolution on the bug tracker (and generally common in software development) that indicates the ticket will not be addressed further. This may be used for acceptable edge cases (for bugs), or enhancements that have been rejected for core inclusion.. (876 tickets currently.)

#scope-creep, #trac