trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: September 2012

Re: [trinity-devel] R14 release plans

From: Darrell Anderson <humanreadable@...>
Date: Thu, 6 Sep 2012 20:55:06 -0700 (PDT)
> That's a lot of bugs!  Right now the release plan looks like this:
> 1.) Resolve the build bug reports or a majority of them
> 2.) Resolve all the blocker bug reports
> 3.) Enter soft freeze, check for new blocker-level bugs
> 4.) Enter hard freeze, distro maintainers recompile packages, check for new bugs again
> 5.) Release!
> 
> 87 bugs is a lot though; looks like we might slip past the
> fall release as well without additional help.

We do need a plan, a set of goals, which is why I raised the question. If we don't set a time line then little will get done. :-(

Yes, I am aware the bulk of the load falls on you. Hopefully others are finished with "summer vacation" and will step forward. I'm always available to test patches.

The good news is the overlap in the posted categories.

Of the 15 Blockers, 9 are Build issues.
Of the 20 Criticals, 8 are build issues.
Of the 65 Majors, 18 are build issues.

Resolving Blockers and Criticals resolves 17 build issues, add Majors and we resolve 35 build issues.

We hit the proverbial two birds with one stone.

Within the build issues, many are repetitive, such as the "...Sym Links Incorrect" (15) and "...unknown icon type" (10). More than likely, after resolving one of each we then have a template for dweebs like me to follow and resolve the remainder.

Using your outline above, I'll propose some goals (pulled out of you-know-where), open to discussion in this list:

Resolve Blocker (15) and Critical (20) bugs by: September 30
Resolve Major Build issues (18) by: October 10
Complete packager testing and related issues by: October 15
Initiate soft freeze: October 15
Resolve New Blocker/Critical/As many Build issue/Major/Normal/Whatever as possible by: October 31
Complete packager testing and related issues by: November 7
Initiate hard freeze: November 10
Initiate usability testing: November 10
Resolve hard freeze bugs by: November 20
Upload tarballs: November 25
Complete final tarball package building by: November 28
Upload packages and allow mirror syncing: November 30
Announce and release: December 3

Darrell