bodhi-3.0.0-0.0.beta[0] has been deployed to staging. We plan to ask for an FBR to deploy the final release when it is ready, but we plan to keep this in testing through Monday, with a theoretical Tuesday production deployment (assuming ACKs and testing goes well).
This is a major release as it is backwards incompatible in how repositories are layed out, and technically the bodhi CLI also has a backwards-incompatibility too (the USERNAME env variable is no longer used, as it clashed with GDM's). Patrick plans to rework the sync script when we deploy to production so this will not impact our users.
The primary purpose of this release is to switch to Pungi instead of mash for repository composition. This allows many things, but the big one is modular repository mashing, which is why we will be asking for a Freeze Break.
[0] https://bodhi.stg.fedoraproject.org/docs/release_notes.html
On 10/19/2017 03:41 PM, Randy Barlow wrote:
bodhi-3.0.0-0.0.beta[0] has been deployed to staging. We plan to ask for an FBR to deploy the final release when it is ready, but we plan to keep this in testing through Monday, with a theoretical Tuesday production deployment (assuming ACKs and testing goes well).
This is a major release as it is backwards incompatible in how repositories are layed out, and technically the bodhi CLI also has a backwards-incompatibility too (the USERNAME env variable is no longer used, as it clashed with GDM's). Patrick plans to rework the sync script when we deploy to production so this will not impact our users.
The primary purpose of this release is to switch to Pungi instead of mash for repository composition. This allows many things, but the big one is modular repository mashing, which is why we will be asking for a Freeze Break.
[0] https://bodhi.stg.fedoraproject.org/docs/release_notes.html
Great work all!
Randy, have we collaborated with Adrian at all? I think mirrormanager will need some updates. See:
https://pagure.io/fedora-infrastructure/issue/6193 https://github.com/fedora-infra/mirrormanager2/issues/215
Also I assume the work for this card is now done:
https://pagure.io/fedora-infrastructure/issue/6192
If so can we update/close that ticket?
Dusty
On 10/19/2017 04:13 PM, Dusty Mabe wrote:
Randy, have we collaborated with Adrian at all? I think mirrormanager will need some updates. See:
https://pagure.io/fedora-infrastructure/issue/6193 https://github.com/fedora-infra/mirrormanager2/issues/215
I believe we only need to update the sync script and MM should just keep working the same as it does today.
Also I assume the work for this card is now done:
https://pagure.io/fedora-infrastructure/issue/6192
If so can we update/close that ticket?
I suppose we should wait until it's actually deployed.
On Thu, Oct 19, 2017 at 03:41:07PM -0400, Randy Barlow wrote:
bodhi-3.0.0-0.0.beta[0] has been deployed to staging. We plan to ask for an FBR to deploy the final release when it is ready, but we plan to keep this in testing through Monday, with a theoretical Tuesday production deployment (assuming ACKs and testing goes well).
This is a major release as it is backwards incompatible in how repositories are layed out, and technically the bodhi CLI also has a backwards-incompatibility too (the USERNAME env variable is no longer used, as it clashed with GDM's). Patrick plans to rework the sync script when we deploy to production so this will not impact our users.
The primary purpose of this release is to switch to Pungi instead of mash for repository composition. This allows many things, but the big one is modular repository mashing, which is why we will be asking for a Freeze Break.
[0] https://bodhi.stg.fedoraproject.org/docs/release_notes.html
Congratulations on (nearly) the 3.0 release! This is a big-deal milestone -- thanks to all who contributed.
infrastructure@lists.fedoraproject.org