[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [linuxtools-dev] Branching strategy for Luna
|
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 something like this:
June: stable-3.x branch (work on SR1, SR1.5 and SR2 happens on this
branch) + v3.0.0 tag
September: v3.1.0 tag ... or 3.0.1 tag
December: v3.2.0 tag ... or 3.0.2 tag
February: v3.3.0 tag ... or 3.0.3 tag or ...
June: v.4.0.0 tag + stable-4.x branch
What do others think?
Marc-Andre
On 14-05-23 04:51 PM, Alexandre Montplaisir wrote:
> Hello Linux Toolers,
>
> I was wondering what is the planned git branching strategy for Luna?
> The API/Feature freeze is next Tuesday, so I assume a stable-3.x
> branch will be created, branching off from master, at that point. Is
> this correct?
>
> Then afterwards, would it be safe to put API-breaking (4.0) changes in
> master? We have a bunch of changes lined up on Gerrit, which are
> currently targeted at master. Most of it won't make it for Luna
> obviously, but we're wondering where we should put them afterwards.
>
> Thanks,
> Alexandre
> _______________________________________________
> linuxtools-dev mailing list
> linuxtools-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/linuxtools-dev
