[linuxtools-dev] Branching strategy for Luna

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[linuxtools-dev] Branching strategy for Luna

From: Alexandre Montplaisir <alexmonthy@xxxxxxxxxxxx>
Date: Fri, 23 May 2014 16:51:11 -0400
Delivered-to: linuxtools-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/linuxtools-dev>
List-help: <mailto:linuxtools-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/linuxtools-dev>, <mailto:linuxtools-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/linuxtools-dev>, <mailto:linuxtools-dev-request@eclipse.org?subject=unsubscribe>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0

Hello Linux Toolers,

I was wondering what is the planned git branching strategy for Luna? TheAPI/Feature freeze is next Tuesday, so I assume a stable-3.x branch willbe created, branching off from master, at that point. Is this correct?

Then afterwards, would it be safe to put API-breaking (4.0) changes inmaster? We have a bunch of changes lined up on Gerrit, which arecurrently targeted at master. Most of it won't make it for Lunaobviously, but we're wondering where we should put them afterwards.


Thanks,
Alexandre

Follow-Ups:
- Re: [linuxtools-dev] Branching strategy for Luna
  - From: Marc-André Laperle

Prev by Date: [linuxtools-dev] [Hudson] Hudson build is back to normal : linuxtools-master #1979
Next by Date: Re: [linuxtools-dev] Branching strategy for Luna
Previous by thread: [linuxtools-dev] Is someone looking at the build failures for the last-minute LTTng changes?
Next by thread: Re: [linuxtools-dev] Branching strategy for Luna
Index(es):
- Date
- Thread

Breadcrumbs