#5911: Rules for private/topic branches in dist-git
Fedora Release Engineering
rel-eng at fedoraproject.org
Thu May 22 08:21:14 UTC 2014
#5911: Rules for private/topic branches in dist-git
--------------------+------------------------
Reporter: hhorak | Owner: rel-eng@…
Type: task | Status: new
Milestone: | Component: git
Keywords: | Blocked By:
Blocking: |
--------------------+------------------------
Since the email to fedora-infra nor fedora-rel-eng ML did not work, I'm
trying my luck here.
I've found a proposal [1] and 'removal manual' [2] for private topic
branches in Fedora dist-git, but no official documentation for that.
What I'm looking for is a way to collaborate on some bigger change between
co-maintainers or keeping a different dist-git content for copr build for
example.
I tried to create one such a topic branch with private- as a prefix and it
seems to work fine. If that is an expected way to do such things, is there
any documentation I just have not found or should we create one?
I believe we should have a documentation at least for:
* rules for naming the private branches (if they should be prefixed by
private-)
* who has rw access for such branches
* how to delete them (is the rel-eng ticket the only way to do it?)
[1] http://fedoraproject.org/wiki/Dist_Git_Branch_Proposal
[2] http://fedoraproject.org/wiki/Dist_Git_Branch_Redux
Bonus: would it be possible to think about creating even new ad-hoc
repositories (with the private branches only)?
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5911>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
More information about the rel-eng
mailing list