#509 change in url for download location after we started using updates composes
Closed: Wontfix a year ago Opened a year ago by dustymabe.

We recently started releasing media that was created as part of the updates composes. A side effect of this is that the directory the media gets copied into has changed it's naming structure.. for example our last release was:

https://dl.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-28-20180806.0/

where our current release is:

https://dl.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180816.1/

This was an undesired change. We need to figure out if we want to keep it this way or change it back. My vote would be that we change it back for the next release.


Metadata Update from @dustymabe:
- Issue tagged with: releng

a year ago

I believe this is only a cosmetic change.
Renaming sub-directory Fedora-28-updates-* to Fedora-Atomic-28-* at https://dl.fedoraproject.org/pub/alt/atomic/stable/ will require changes at multiple places because so far we have same name for artifacts directory and compose ID.
Some of the changes which will be required if really want to do this are:
1. releg push-twoweek script which publishes fedmsg e.g. https://apps.fedoraproject.org/datagrepper/id?id=2018-6923dab4-3815-45bd-ba26-f92f5e9beeff&is_raw=true&size=extra-large
2. releg push-twoweek script where we prepare link for release artifacts we produce
3. fedora-Website repo

This will need careful effort to make sure we don't miss something.

so your recommendation is that we leave it like it is and don't make the change?

I am a bit leaned towards not making this change because in the end what user download is the image artifacts and media filenames matches with what we used to ship previously :)

If we are not yet sure, maybe we should get opinion from other community members?

I am a bit leaned towards not making this change because in the end what user download is the image artifacts and media filenames matches with what we used to ship previously :)

I'm fine with that but it might get a little confusing around major release time. Do you mind sending an email to atomic-devel to let people know about the change in case they were depending on the file structure for some reason?

Yup, will send an email.

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

a year ago

Login to comment on this ticket.

Metadata