#7411 Create Fedora 28 Beta candidates
Closed: Fixed 6 years ago Opened 6 years ago by adamwill.

Can we please have a Beta release candidate compose, with the following in addition to the packages that have just been pushed stable in the latest stable push:

== Blockers ==

== Freeze exceptions ==

Please remember all appropriate steps for release candidate composes. Thanks!


Compose is done and available from ​​https://kojipkgs.fedoraproject.org/compose/28/Fedora-28-20180326.0/compose/ it has been synced to ​​http://dl.fedoraproject.org/pub/alt/stage/28_Beta-1.1/ rpms have all be hardlinked to /pub/fedora/linux/development/28/

Metadata Update from @mohanboddu:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

6 years ago

I'm requesting a Beta-1.2 compose. This one is unusual in that there are no blockers to fix. Instead I'm requesting a compose with one update to fix an FE issue:

and also with this workstation-ostree-config change which should fix a showstopper issue for FAW: I believe you do not need to do anything special for that change to take effect in the compose, @dustymabe or @walters should know for sure.

These two changes fix a couple of serious issues in FAH and FAW. While these aren't technically release blocking, that's more about procedural issues than importance, we do care about Atomic - especially FAH - quite a lot and want it to work properly at Beta. So I think it makes sense to have a new compose, even though technically we aren't supposed to compose unless a blocker needs fixing.

If there turn out to be serious issues in Beta-1.2, we would still have the option of shipping Beta-1.1.

Metadata Update from @adamwill:
- Issue status updated to: Open (was: Closed)

6 years ago

I believe you do not need to do anything special for that change to take effect in the compose

correct

we do care about Atomic - especially FAH - quite a lot and want it to work properly at Beta

+1 - we have discussed adding some wording to the criteria to this effect, but have not officially done that yet.

Please use systemd-238-7.fc28 instead of systemd-238-6.fc28. systemd-238-6.fc28 is buggy on non-atomic.

Please use systemd-238-7.fc28 instead of systemd-238-6.fc28. systemd-238-6.fc28 is buggy on non-atomic.

Well, we made a good attempt. I guess we'll just have to use Beta-1.1.

Compose is done and available from ​​https://kojipkgs.fedoraproject.org/compose/28/Fedora-28-20180328.0/compose/ it has been synced to ​​http://dl.fedoraproject.org/pub/alt/stage/28_Beta-1.2/ rpms have all be hardlinked to /pub/fedora/linux/development/28/

Metadata Update from @mohanboddu:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

6 years ago

I figure we can go ahead and fire a 1.3, with:

Same update as before, but I edited it to -7.

Having a 1.3 compose gives us at least the option of shipping it, if we can test it sufficiently in time. We can still decide to ship 1.1 if we think 1.3 is too risky. Again, I won't submit a systemd update to stable till we're sure which one we want to go with.

Metadata Update from @adamwill:
- Issue status updated to: Open (was: Closed)

6 years ago

Compose is done and available from ​​https://kojipkgs.fedoraproject.org/compose/28/Fedora-28-20180328.1/compose/ it has been synced to ​​http://dl.fedoraproject.org/pub/alt/stage/28_Beta-1.3/ rpms have all be hardlinked to /pub/fedora/linux/development/28/

Metadata Update from @mohanboddu:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

6 years ago

Login to comment on this ticket.

Metadata