On Thu, May 28, 2009 at 10:36:18AM -0700, Jesse Keating wrote:
A late discovered and just potentially fixed anaconda storage bug[1] has necessitated another week slip of our schedule. The change is important but invasive enough to require re-validating our storage tests. We were already late in producing the Release Candidate and there is not enough time to produce another one and validate it in time for next Tuesday's release date. Therefor we have decided to enact another week long slip of the release. This gives us time to create a second release candidate and fully validate it and hand it off to the mirrors in plenty of time to sync up for the new release date of June 9th. As much as we regret slipping, we also wish to avoid easily trigger-able bugs in our release, particularly in software that cannot be fixed with a 0-day update.
At this time we would only accept tag requests for critical issues.
Does it make sense to fold in the f11 updates into the next preview release? E.g. to move all current updates back to rawhide?
Axel Thimm wrote:
On Thu, May 28, 2009 at 10:36:18AM -0700, Jesse Keating wrote:
A late discovered and just potentially fixed anaconda storage bug[1] has necessitated another week slip of our schedule. The change is important but invasive enough to require re-validating our storage tests. We were already late in producing the Release Candidate and there is not enough time to produce another one and validate it in time for next Tuesday's release date. Therefor we have decided to enact another week long slip of the release. This gives us time to create a second release candidate and fully validate it and hand it off to the mirrors in plenty of time to sync up for the new release date of June 9th. As much as we regret slipping, we also wish to avoid easily trigger-able bugs in our release, particularly in software that cannot be fixed with a 0-day update.
At this time we would only accept tag requests for critical issues.
Does it make sense to fold in the f11 updates into the next preview release? E.g. to move all current updates back to rawhide?
Little sense imo... no/little qa/testing, more work, more delay.
-- Rex
On Fri, May 29, 2009 at 09:16:39AM -0500, Rex Dieter wrote:
Axel Thimm wrote:
On Thu, May 28, 2009 at 10:36:18AM -0700, Jesse Keating wrote:
A late discovered and just potentially fixed anaconda storage bug[1] has necessitated another week slip of our schedule. The change is important but invasive enough to require re-validating our storage tests. We were already late in producing the Release Candidate and there is not enough time to produce another one and validate it in time for next Tuesday's release date. Therefor we have decided to enact another week long slip of the release. This gives us time to create a second release candidate and fully validate it and hand it off to the mirrors in plenty of time to sync up for the new release date of June 9th. As much as we regret slipping, we also wish to avoid easily trigger-able bugs in our release, particularly in software that cannot be fixed with a 0-day update.
At this time we would only accept tag requests for critical issues.
Does it make sense to fold in the f11 updates into the next preview release? E.g. to move all current updates back to rawhide?
Little sense imo... no/little qa/testing, more work, more delay.
Maybe that's even a reason to pull them in now. After all these 600+ packages will be on every F11 system from the first day, so if there is a problem, we better stumble over it now.
Axel Thimm wrote:
On Fri, May 29, 2009 at 09:16:39AM -0500, Rex Dieter wrote:
Axel Thimm wrote:
Does it make sense to fold in the f11 updates into the next preview release? E.g. to move all current updates back to rawhide?
Little sense imo... no/little qa/testing, more work, more delay.
Maybe that's even a reason to pull them in now. After all these 600+ packages will be on every F11 system from the first day, so if there is a problem, we better stumble over it now.
Sorry, let me be clearer, ... no/little qa/testing of the spins/images...
-- Rex
On Fri, May 29, 2009 at 18:07:12 +0300, Axel Thimm Axel.Thimm@ATrpms.net wrote:
Maybe that's even a reason to pull them in now. After all these 600+ packages will be on every F11 system from the first day, so if there is a problem, we better stumble over it now.
I am testing rawhides + updates + updates-testing actively on two machines (and have it running on two more I am not using very actively). I have been seeing downgrades of packages happening (thanks to Seth for the yum downgrade feature to make fixing this easy), so I am guessing that other people are also doing this and have been reporting problems to Bohdi, resulting in several packages getting yanked from updates-testing.
On Fri, May 29, 2009 at 16:24:01 +0300, Axel Thimm Axel.Thimm@ATrpms.net wrote:
Does it make sense to fold in the f11 updates into the next preview release? E.g. to move all current updates back to rawhide?
I think the object is to get iso's that will boot and install properly with F11. Fixing bugs not related that isn't nearly as important, as once the image is installed people can get the latest updates. From that perspective, the extra work verifying that the updates don't break booting and installing under lots of different circumstances isn't worth it.
And people who want to make their own spins can already do this when they need it. So merging in today's updates aren't that important, since they would want to get the updates at some future point in time.
-
Axel Thimm -
Bruno Wolff III -
Rex Dieter