On Fri, Dec 04, 2020 at 06:11:40AM -0500, Pavel Valena wrote: > ----- Original Message ----- > > From: "Till Maas" <opensource@xxxxxxxxx> > > To: "Development discussions related to Fedora" <devel@xxxxxxxxxxxxxxxxxxxxxxx> > > Sent: Friday, December 4, 2020 11:09:27 AM > > Subject: Re: Fedora 34 Change: GitRepos-master-to-main (Self-Contained Change) > > > > On Thu, Dec 03, 2020 at 08:52:13PM +0100, Pierre-Yves Chibon wrote: > > > > > After looking at the infra and releng issue trackers Kevin managed to found > > > back > > > the ticket I was thinking about. > > > You have my apologies, the namespace that was asking to a different default > > > branch and for that branch to not be named "rawhide" was flatpaks. > > > They wanted the default branch to be "stable", which would not apply to > > > most > > > other namespaces. Thus the proposal to go with "main" which works for all > > > namespaces and seems to be on its way to become the industry standard. > > > > The flatpak namespace considering "main" to be the stable branch but > > rpms considering "main" to be the development branch, is IMHO an > > argument why we flatpack should use "stable" and rpms "rawhide". This > > will make it more clear for everyone what the branch is actually about. > > I agree. "main" is still quite ambiguous - is it stable? is it devel? It's the main branch where things take place. ;) > And "rawhide" would correspond with the repo... Is there any show-stopper that I've missed? I don't think you can make branches completely descripive by themselves, unless possibly you make them really long. flatpak_branch_where_stable_flatpaks_are_made_from rawhide_its_the_branch_for_the_development_version_of_fedora_called_rawhide So, IMHO, we are overcomplicating it, and we should just use main. I suppose it's ok to make 'rawhide' a symref to main, or 'stable' in the flatpak case... kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
