Hi,
On Tue, Sep 15, 2015 at 10:48 PM, Edward Burns <edward.burns_at_oracle.com> wrote:
>>>>>> On Tue, 15 Sep 2015 13:50:00 -0500, manfred riem <manfred.riem_at_oracle.com> said:
> You can still use topic branches and push
> them to the remote but the responsibility of merging the topic branch to
> master lies with each committer.
Would it perhaps be an option to use actual feature branches for this
in the java.net git repo, one for each committer and for now for the
2.3 branch only?
That way you can follow the first part (seen from the left) of the
diagram depicted at the start of this article:
http://nvie.com/posts/a-successful-git-branching-mode
Practically I could then work on my own feature branch, then push
there as often as I want to share my still in development changes with
the world. E.g. show them to Bauke, the EG, etc and work on that
branch from different systems (e.g. my laptop, workstation, etc). Then
when the feature is deemed complete I can merge and/or cherry pick it
myself into the (local) 2.3 main branch and make the diff for review,
and eventually push it.
Thoughts?
Kind regards,
Arjan Tijms
>
> Hopefully we'll just be able to move to github and make this easier.
>
> Thanks,