All,
I am now officially back from my holiday vacation away from TDE.
I would like to get R14.0.0 squared away and out the door in the next few months if possible; thoughts on the current status of the nightly builds are welcome. I know quite a few bugs remain, however many critical bugs have been repaired and I don't want to hold those fixes (which cannot be ported to the 3.5.13.x series) back much longer.
How does a tentative release date of April 15, 2013 sound? This means that the remaining blocker bugs need to be resolved by February 2013 in order to get the R14 release candidate into the hands of our QA team with sufficient time for them to find and resolve quality problems before release. A tentative final source release date would be March 15; this would allow 2 weeks for the binary build maintainers to update their packages before release, and a week or two for the mirrors to sync with the new packages.
For me the biggest blocker bug remaining is the XDG icon naming issue (http://bugs.pearsoncomputing.net/show_bug.cgi?id=1313), as this causes a very bad (inconsistent) user experience with most non-TDE software packages. I will be working hard to resolve that issue; if each developer here could find a large blocker bug and work on fixing it over the next few weeks that would be great!
Tim
On 2 January 2013 20:47, Timothy Pearson kb9vqf@pearsoncomputing.net wrote:
All,
I am now officially back from my holiday vacation away from TDE.
Hope you enjoyed your holidays!
I would like to get R14.0.0 squared away and out the door in the next few months if possible; thoughts on the current status of the nightly builds are welcome. I know quite a few bugs remain, however many critical bugs have been repaired and I don't want to hold those fixes (which cannot be ported to the 3.5.13.x series) back much longer.
Looks like we have 38 total critical and blocker bugs to resolve.
How does a tentative release date of April 15, 2013 sound? This means that the remaining blocker bugs need to be resolved by February 2013 in order to get the R14 release candidate into the hands of our QA team with sufficient time for them to find and resolve quality problems before release. A tentative final source release date would be March 15; this would allow 2 weeks for the binary build maintainers to update their packages before release, and a week or two for the mirrors to sync with the new packages.
Not to mention documentation, press release, and such getting done before the release. I think those last two weeks during the mirror setup should be also for that.
Calvin
On Thursday 03 of January 2013 02:47:34 Timothy Pearson wrote:
All,
I am now officially back from my holiday vacation away from TDE.
I would like to get R14.0.0 squared away and out the door in the next few months if possible; thoughts on the current status of the nightly builds are welcome. I know quite a few bugs remain, however many critical bugs have been repaired and I don't want to hold those fixes (which cannot be ported to the 3.5.13.x series) back much longer.
Definitely - it would be good to have R14 of the door as soon as possible. But just as surely we must have serious problems resolved before a new version is released.
How does a tentative release date of April 15, 2013 sound? This means that the remaining blocker bugs need to be resolved by February 2013 in order to get the R14 release candidate into the hands of our QA team with sufficient time for them to find and resolve quality problems before release. A tentative final source release date would be March 15; this would allow 2 weeks for the binary build maintainers to update their packages before release, and a week or two for the mirrors to sync with the new packages.
Note the dates that are in the draft R14.0.0 Road Map in Etherpad - http://trinity.etherpad.trinitydesktop.org/39 - there is little similarity with your proposal. Just a little less optimistic.
For me the biggest blocker bug remaining is the XDG icon naming issue (http://bugs.pearsoncomputing.net/show_bug.cgi?id=1313), as this causes a very bad (inconsistent) user experience with most non-TDE software packages. I will be working hard to resolve that issue; if each developer here could find a large blocker bug and work on fixing it over the next few weeks that would be great!
Tim
Slavek
-
Calvin Morrison -
Slávek Banko -
Timothy Pearson