dustymabe added a new comment to an issue you are following: `` > I'm not sure I understand. If you want a new unified repo to be brand new, > that's fine w/ me. I just want to get rid of the separate refs for each major > version / required rebase nonsense. >
I'm just saying that I don't really want a "unified repo", but that I do agree with you that I'd like to make the user experience a good one to the point they don't even know they are getting rebased unless they look at the logs or explicitly configure the client to not do that. This would give us a good operational experience (as we can clearly make big changes to the backend repo periodically) as well as a good user experience (they don't need to do anything other than what they are already doing). > > You're ignoring the second part of my sentence: "And places like the kube > ansible scripts, which call on atlas for the vagrant boxes, need updates each > time fedora atomic revs, where centos atomic is always accessible at > centos/atomic-host." We have fedora/23-atomic-host, fedora/24-atomic-host, > fedora/25-atomic-host, where we should have fedora/atomic-host. It's another > place where arbitrarily splitting up fedora atomic causes inconvenience. I see what you mean. yes we can chat about that as well. Like I said I still see value in being able to grab the older versions, but we don't allow for that today since we delete them after some time, so having f24/f25, etc doesn't really give us value. I think let's discuss this change maybe in a separate ticket? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/231 _______________________________________________ cloud mailing list -- [email protected] To unsubscribe send an email to [email protected]
