dustymabe added a new comment to an issue you are following: `` We met today to discuss what a rolling release would look like for fedora atomic host. The notes from the [etherpad](https://public.etherpad-mozilla.org/p/20170317-FAH-rollingrelease) we used during the meeting are attached. Here is a summary: - We would like to make it seamless for users to follow the latest released FAH (including across major number releases of Fedora) - We can achieve this in a couple of ways. 1st is by having a `stable` or `latest` ref in our repo that is a symbolic link to the ref that follows a particular release. i.e. for now `latest` -> `f25`. Once f26 is out we would update the symbolic link. This would require a single unified ostree repo. - 2nd would be to point users at a "remote" that is essentially a URL redirect that represents `stable` or `latest` and keep the ref names the same in the individual (f25,f26) ostree repos. This way the "remote" url could be switched easily. If this "works" it would allow us to keep ostree repos separate for each major release of Fedora. If we decide the first one is what we would want to do (i believe this was the consensus in the meeting) then there are some possible work items: - work to make a unified repo - need to set up tooling for pruning the ostree repo - sym link needs to be updated when new NUMBER release is first released - ostree creation process needs to point to new unified repo - 2wk script needs to be updated to update unified repo - Ensure that all relevant groups throughout Fedora (Releng, QA, Websites) know what the plan is and how it could impact them (also be willing to do the work to make it happen if extra work is needed) - We can achieve this by storing a symbo - should probably Here are the meeting notes [](/atomic-wg/issue/raw/files/77160a75700a35be005c9f85d7fb1acdb62fe43494b0d51f1d9f0e944726a717-20170317-FAH-rollingrelease.html) `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/231 _______________________________________________ cloud mailing list -- cloud@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to cloud-leave@xxxxxxxxxxxxxxxxxxxxxxx
