Wednesday 17 March 2021

Re: General mechanism to supply "rich history" to git-ubuntu

My preference would be to open up some refs of git-ubuntu repositories to uploaders to be read&write.

Such that one could created dgit like uploads and push the commit id, as a ref, into the git-ubuntu repository directly. Aka refs/heads/uploads/commit-hash as a branch.

Then upon import git-ubuntu could look up the Dgit header from the dsc, and check if it knows about refs/heads/uploads/Dgit-header-from and reuse that as part of the archive-matching set of branches.

Separately, I also want team uploads to be open to coredevs in the git-ubuntu repositories, i.e. such that there is no need to create ~ubuntu-core-dev/ubuntu/+source/$package repositories and instead the main git-ubuntu repository has refs/heads/teams/ubuntu-core-dev/* namespace available for ubuntu-core-devs to push using per-ref ACLs in Launchpad. This would finally enable to target merge proposals to git-ubuntu repository, merge them, and for those commits to end up as part of the git-ubuntu locked branches history via above /uploads/ namespace.

I do not want to maintain additional repositories, neither short or long term, outside of the git-ubuntu ones. And keep a 1-to-1 mapping with them.

The goal is to allow merging merge proposals into the git-ubuntu repository namespaced refs. And for them to end up in the git-ubuntu managed refs, if and when, the matching upload of those changes is accepted in the archive.