I am very much in favor of having the master branch be the "unstable"
Mars branch. It think it makes sense to have master always going and
branch off the more stable branches from it. That way, development that
includes major changes (API breaking) is not stalled.
I was thinking we could do someth
Please be advised that I have created the stable-3.0 branch. Any subsequent
changes meant for Luna RC2, RC3, or RC4 should be cherry-picked from master.
Please
update your remotes to add a gerrit instance for stable-3.0.
-- Jeff J.
___
linuxtools-dev
Hi Jeff,
I'm unable to push to the stable-3.0 branch.
remote: error: insufficient permission for adding an object to repository
database ./objects
Patrick
On Mon, May 26, 2014 at 12:06 PM, Jeff Johnston wrote:
> Please be advised that I have created the stable-3.0 branch. Any
> subsequent
>
By any chance did you try pushing directly to the branch? You need
to push to a gerrit remote which specifies that branch as the target:
[remote "review-3.0"]
url =
ssh://jjohns...@git.eclipse.org:29418/linuxtools/org.eclipse.linuxtools.git
push = HEAD:refs/for/stable-3.0
Cool! so now can we use @since 3.1 in code and @since 4.0?
On 14-05-26 12:06 PM, Jeff Johnston wrote:
> Please be advised that I have created the stable-3.0 branch. Any subsequent
> changes meant for Luna RC2, RC3, or RC4 should be cherry-picked from master.
> Please
> update your remotes to a
The stable-3.0 branch has been created. Basically, a new branch is created
around RC1
time so we can ensure people aren't jamming new features into the build. I have
requested a new Hudson job for building this new branch.
Whether we put API-breaking stuff into master usually has depended on ho
As soon as I have the new Hudson job working, yes. So hold off a
bit.
-- Jeff J.
- Original Message -
From: "Matthew Khouzam"
To: linuxtools-dev@eclipse.org
Sent: Monday, May 26, 2014 3:48:37 PM
Subject: Re: [linuxtools-dev] stable-3.0 branch created
Cool! so now can we use @since 3.1
Hi Jeff,
We were hoping to be able to push without review patches that have been
cherry-picked from a patch that was already reviewed on master branch. Is
it OK to push through the gerrit remote with HEAD:refs/heads/stable-3.0?
By the way is it only the stable-3.0 branch that doesn't allow pushin
