R14 release plans - tde-devels - Trinity Desktop Environment

List overview All Threads
Download

R14 release plans

amarok - postgres support

Reducing xession log spew

Darrell Anderson

6 Sep 2012 6 Sep '12

2:28 p.m.

In the latest Trinity news release: The Trinity development team has adopted a "release when ready" approach but tentatively are focused on releasing R14.0.0 in the fall of 2012. What is the definition of fall of 2012? Meteorological fall is ~September 21 to ~December 21. Traditional fall is September to November. Do we have a release plan at all? Darrell

Reply

Show replies by date

Jonesy

6 Sep 6 Sep

3:42 p.m.

New subject: [trinity-devel] R14 release plans

On Thu, 6 Sep 2012, Darrell Anderson wrote:

In the latest Trinity news release: The Trinity development team has adopted a "release when ready" approach but tentatively are focused on releasing R14.0.0 in the fall of 2012. What is the definition of fall of 2012? Meteorological fall is ~September 21 to ~December 21. Traditional fall is September to November.

In which hemisphere? :-) Jonesy

Reply

Timothy Pearson

5:34 p.m.

New subject: [trinity-devel] R14 release plans

In the latest Trinity news release: The Trinity development team has adopted a "release when ready" approach but tentatively are focused on releasing R14.0.0 in the fall of 2012. What is the definition of fall of 2012? Meteorological fall is ~September 21 to ~December 21. Traditional fall is September to November. Do we have a release plan at all? Darrell

How many blocker bugs remain? As far as I know unresolved Blocker/Critical bug reports are the only major item holding up the R14 release. Tim

Reply

Darrell Anderson

6:43 p.m.

New subject: [trinity-devel] R14 release plans

How many blocker bugs remain? As far as I know unresolved Blocker/Critical bug reports are the only major item holding up the R14 release.

Blocker: 15 http://bugs.trinitydesktop.org/buglist.cgi?cmdtype=runnamed&namedcmd=Bl… Critical: 20 http://bugs.trinitydesktop.org/buglist.cgi?cmdtype=runnamed&namedcmd=Cr… Major: 65 http://bugs.trinitydesktop.org/buglist.cgi?cmdtype=runnamed&namedcmd=Ma… Regressions: 12 http://bugs.trinitydesktop.org/buglist.cgi?cmdtype=runnamed&namedcmd=Re… Build issues: 87 http://bugs.trinitydesktop.org/buglist.cgi?cmdtype=runnamed&namedcmd=Bu… Darrell

Reply

Timothy Pearson

7:23 p.m.

New subject: [trinity-devel] R14 release plans

How many blocker bugs remain? As far as I know unresolved Blocker/Critical bug reports are the only major item holding up the R14 release.

Blocker: 15 http://bugs.trinitydesktop.org/buglist.cgi?cmdtype=runnamed&namedcmd=Bl… Critical: 20 http://bugs.trinitydesktop.org/buglist.cgi?cmdtype=runnamed&namedcmd=Cr… Major: 65 http://bugs.trinitydesktop.org/buglist.cgi?cmdtype=runnamed&namedcmd=Ma… Regressions: 12 http://bugs.trinitydesktop.org/buglist.cgi?cmdtype=runnamed&namedcmd=Re… Build issues: 87 http://bugs.trinitydesktop.org/buglist.cgi?cmdtype=runnamed&namedcmd=Bu… Darrell

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. Tim

Reply

Calvin Morrison

8:32 p.m.

New subject: [trinity-devel] R14 release plans

On 6 September 2012 22:23, Timothy Pearson <kb9vqf(a)pearsoncomputing.net> wrote:

How many blocker bugs remain? As far as I know unresolved Blocker/Critical bug reports are the only major item holding up the R14 release.

Blocker: 15 http://bugs.trinitydesktop.org/buglist.cgi?cmdtype=runnamed&namedcmd=Bl… Critical: 20 http://bugs.trinitydesktop.org/buglist.cgi?cmdtype=runnamed&namedcmd=Cr… Major: 65 http://bugs.trinitydesktop.org/buglist.cgi?cmdtype=runnamed&namedcmd=Ma… Regressions: 12 http://bugs.trinitydesktop.org/buglist.cgi?cmdtype=runnamed&namedcmd=Re… Build issues: 87 http://bugs.trinitydesktop.org/buglist.cgi?cmdtype=runnamed&namedcmd=Bu… Darrell

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. Tim --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting

what about 3.5.13.1? when does that get released? at this point 3.5.13.1 will be released in the fall and R14 in the spring. It is better to be realistic than pull a KDE4.0 Calvin

Reply

Darrell Anderson

8:58 p.m.

New subject: [trinity-devel] R14 release plans

what about 3.5.13.1? when does that get released? at this point 3.5.13.1 will be released in the fall and R14 in the spring. It is better to be realistic than pull a KDE4.0

My understanding is 3.5.13.1 is "any day now." "Fall of 2012" to me sounds like November or early December. That is a three month gap. Set a goal of R14 in the spring and little will get done --- human nature. Darrell

Reply

Darrell Anderson

8:55 p.m.

New subject: [trinity-devel] R14 release plans

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

Reply

4269

days inactive

4270

days old

devels@trinitydesktop.org

Manage subscription

7 comments

4 participants

tags (0)

participants (4)

Calvin Morrison
Darrell Anderson
Jonesy
Timothy Pearson