Learn more about these different git repos.
Other Git URLs
Recently someone asked if there is a easy way to help packagers get notified from EOL branch, which is also helpful for upgradepath check, my opinion get no response however I still want to mention it here:
But here comes a problem, Fedora allows packagers to commit to the EOL branch(and even there is a badge[1] is for this "achievement", IMO it's really nonsense for packagers to commit to the EOL branches, ludicrous)
If it's commitable, then go ahead like normal.
If not, return a message to packagers, tell them that branch(with mapping to the actual release but not just a simple branch name) is abandoned.
Then git pull --rebase, handled by fedpkg. Should add a switch branch action to remap the branches, not sure.
Fine again, notify packagers finish the work.
In spite of the above can solve the problem IMO, the strategy of the commit to the EOL branches should be enhanced still.
[1]------https://badges.fedoraproject.org/badge/you-can-pry-it-from-my-cold%2C-undead-hands
One of the big benefits of dist-git and fedpkg is so that you can do your work while being entirely offline. adding checkking into fedpkg breaks its ability to work networkless for doing development work or it means you have to add a manually created list that needs frequent updating and is easy to circumvent.
Adding something on the server would mean much greater complexity in the acl system and add another manual step at release EOL.
I really do not see the benefit of implementing any of this, we remove the ability to build for EOL releases in koji, the commits cause no actual harm.
As it is I and I suspect most developers mostly use git and not fedpkg to do commits and change branches etc, so adding checks to fedpkg gets us very little.
Metadata Update from @cicku: - Issue set to the milestone: Fedora 21 Final
Login to comment on this ticket.