Just a reminder the final "full freeze" starts on November 11th. That means we've got a week to get any changes we want in and ready.
-Mike
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Mike McGrath wrote:
Just a reminder the final "full freeze" starts on November 11th. That means we've got a week to get any changes we want in and ready.
I thought that we're already "frozen" ? (aside from critical/stopper fixes which are filed as per
https://fedoraproject.org/wiki/ReleaseEngineering/FinalFreezePolicy
yes?
-Mike
Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
- -- +---------------------------------------------------------------------+
Please also check the log file at "/dev/null" for additional information. (from /var/log/Xorg.setup.log)
| Greg Hosler ghosler@redhat.com | +---------------------------------------------------------------------+
Gregory Hosler wrote:
Mike McGrath wrote:
Just a reminder the final "full freeze" starts on November 11th. That means we've got a week to get any changes we want in and ready.
I thought that we're already "frozen" ? (aside from critical/stopper fixes which are filed as per
https://fedoraproject.org/wiki/ReleaseEngineering/FinalFreezePolicy
yes?
Different freeze. Mike's talking about the Infrastructure freeze. (We don't make changes to infrastructure near to release time so that we don't destabilize building and delivering packages right around release.)
-Toshio
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Toshio Kuratomi wrote:
Gregory Hosler wrote:
Mike McGrath wrote:
Just a reminder the final "full freeze" starts on November 11th. That means we've got a week to get any changes we want in and ready.
I thought that we're already "frozen" ? (aside from critical/stopper fixes which are filed as per
https://fedoraproject.org/wiki/ReleaseEngineering/FinalFreezePolicy
yes?
Different freeze. Mike's talking about the Infrastructure freeze. (We don't make changes to infrastructure near to release time so that we don't destabilize building and delivering packages right around release.)
So, can packages (already in F10) be updated ?
I tried to do a "make build" in my package "devel" branch last night, and I got the following error message:
koji: error: Destination tag dist-f10 is locked
I took this to mean that packages cannot be updated until after the release ?
- -Greg
-Toshio
Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
- -- +---------------------------------------------------------------------+
Please also check the log file at "/dev/null" for additional information. (from /var/log/Xorg.setup.log)
| Greg Hosler ghosler@redhat.com | +---------------------------------------------------------------------+
On Fri, 2008-11-07 at 11:24 +0800, Gregory Hosler wrote:
I tried to do a "make build" in my package "devel" branch last night, and I got the following error message:
koji: error: Destination tag dist-f10 is locked
I took this to mean that packages cannot be updated until after the release ?
Do a cvs up -d from your module/ directory so that it updates your common/ folder. It'll set up your build target correctly.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Jesse Keating wrote:
On Fri, 2008-11-07 at 11:24 +0800, Gregory Hosler wrote:
I tried to do a "make build" in my package "devel" branch last night, and I got the following error message:
koji: error: Destination tag dist-f10 is locked
I took this to mean that packages cannot be updated until after the release ?
Do a cvs up -d from your module/ directory so that it updates your common/ folder. It'll set up your build target correctly.
ah ha.
Will building in the newly created F-10 directory become a "0 day" update ?
Thank you, and all the best,
- -Greg
Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
- -- +---------------------------------------------------------------------+
Please also check the log file at "/dev/null" for additional information. (from /var/log/Xorg.setup.log)
| Greg Hosler ghosler@redhat.com | +---------------------------------------------------------------------+
On Thu, Nov 6, 2008 at 11:02 PM, Gregory Hosler ghosler@redhat.com wrote:
Will building in the newly created F-10 directory become a "0 day" update ?
Not automatically, you still have to submit the update via bodhi (make update). However, CVS is down right at the moment for the F-10 mass branching :)
On Fri, 2008-11-07 at 12:02 +0800, Gregory Hosler wrote:
Will building in the newly created F-10 directory become a "0 day" update ?
If you use bodhi and request it as an update, yes.
On 2008-11-07 10:35:35 AM, Gregory Hosler wrote:
Mike McGrath wrote:
Just a reminder the final "full freeze" starts on November 11th. That means we've got a week to get any changes we want in and ready.
I thought that we're already "frozen" ? (aside from critical/stopper fixes which are filed as per
I think that freeze is for packages - Mike was referring to the infrastructure freeze (changes to our systems).
Thanks, Ricky
Mike McGrath wrote:
Just a reminder the final "full freeze" starts on November 11th. That means we've got a week to get any changes we want in and ready.
I thought that we're already "frozen" ? (aside from critical/stopper fixes which are filed as per
I think that freeze is for packages - Mike was referring to the infrastructure freeze (changes to our systems).
Thanks, Ricky
Yep, as per the link Mike posted ( https://fedoraproject.org/wiki/ReleaseEngineering/FinalFreezePolicy), it says "no new builds are allowed for packages already in the Fedora collection" which is a package freeze :D -Anand
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Anand Capur wrote:
Mike McGrath wrote:
Just a reminder the final "full freeze" starts on November 11th. That means we've got a week to get any changes we want in and ready.
I thought that we're already "frozen" ? (aside from critical/stopper fixes which are filed as per
I think that freeze is for packages - Mike was referring to the infrastructure freeze (changes to our systems).
Thanks, Ricky
Yep, as per the link Mike posted ( https://fedoraproject.org/wiki/ReleaseEngineering/FinalFreezePolicy), it says "no new builds are allowed for packages already in the Fedora collection" which is a package freeze :D
ah. ok. now I understand.
Thank you, all, for the clarification. (and sorry for the confusion).
Might I know, please, how do we prepare a "0 day" update ? (an update that is ready on the day of the release, but not part of the release).
Thank you, and all the best,
- -Greg
-Anand
Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
- -- +---------------------------------------------------------------------+
Please also check the log file at "/dev/null" for additional information. (from /var/log/Xorg.setup.log)
| Greg Hosler ghosler@redhat.com | +---------------------------------------------------------------------+
infrastructure@lists.fedoraproject.org