On Thu, Aug 25, 2016 at 5:43 PM, Adam Miller
I just wanted to throw out a note to everyone that I've gotten a chance
to work on this and pending some testing we should be good to go for next
Two Week Atomic Release ... however, this is going to cause issues where the
download link is broken for an unknown period of time while two things
1) the website renders post fedmsg about the release being done
2) the mirrors checking in to sync the new data.
This likely won't be a massive problem as we've seen some inconsistency with
the download link due to mirrors sync'ing in the past (because we don't have
a way to intelligently "teach" MirrorManager about the images like we can
for yum/dnf repo metadata so the metalink isn't pruned dynamically), but I
wanted to be sure and mention it.
Once the change is made, the new download location will be:
We will maintain a N and N-1 of $COMPOSE_ID directories in the stable/ base
We will also now have a 'latest' directory that will always point to the
latest stable content:
This change is not finalized at this time so if there are any requested
alterations, please make them between now and the next Two Week Release.
Just a quick update, after some initial code review it was pointed out
that the "latest" target would be better handled via a web end point
that would auto-update with the data we're already providing via
fedmsg as part of the release process. I'm going to refactor the code
to only handle the N and N+1 stable release hosting and then work with
the websites team to handle the "latest" download target.
>  - https://fedorahosted.org/cloud/ticket/147
>  - https://pagure.io/releng/pull-request/101