Hi, Ernesto,
You are correct that streams/0.9-maintenance would be for development of 0.9.x service releases after 0.9.
If it’s just a small-ish bug that you’re working on, I’d recommend the Papyrus convention of bugs/<number>, which I think many Eclipse projects use. Otherwise, if it’s a topic branch, the best is committers/<name>/<topic>. That’s also a Papyrus convention and in general use in other Eclipse projects.
Zeligsoft isn’t a committer, so that would look a bit odd. I seem to recall that the Eclipse Git server has permission rules that recognize the “committers/<committer-id>” pattern and let the matching committer do whatever (s)he likes in there, including non-fast-forward pushes and other destructive actions.
We try to use only these three branching naming patterns in the Papyrus project; there are historical deviations from before we agreed on these.
On 19 October, 2016 at 11:08:42, Ernesto Posse (eposse@xxxxxxxxxxxxx) wrote:
Hello everyone.
Young-Soo and I are already working on some port-0.8 bugs and
Simon wants to have a branch for this. So we want to create a
branch but we are not sure what to call it. Checking the Papyrus
conventions, it looks like branch naming follows one of these
forms:
bugs/<number>
committers/<name>/<topic>
streams/<major.minor>-maintenance
Are there any other forms?
So I was wondering if we should create
streams/0.9-maintenance
although the name sounds misleading. My understanding is that
the 'maintenance' branches are for commits after the release. Is
that right?
How about something like
streams/0.9-prerelease
or something like that? The idea is that the "prerelease"
branch would be rebased onto master once 0.8 is
released.
And if there are objections to that, maybe we do one just for
us (Zeligsoft), perhaps
committers/zeligsoft/0.9
?
Thoughts?
--
Ernesto Posse
Zeligsoft
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
|