[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [mylyn-versions-dev] API freeze branching
|
In the past we have tried avoiding branching except for service
releases. Branching is somewhat painful with CVS and tracking changes
on multiple branches creates extra overhead.
Since the release is only two weeks away I would prefer if we could
block head for that time frame and do the feature work in branches.
Once we move all projects to Git I'd be happy to define a policy to
branch right after API freeze or something like that.
Does that make sense?
Steffen
On Wed, Mar 2, 2011 at 2:22 PM, alvaro sanchez <alvsan09@xxxxxxxxx> wrote:
> Hello,
> As mentioned earlier in R4E we are not ready to participate in the API
> freeze for the 0.7 release,
> so to avoid conflicts we started updates in Mylyn Versions from a
> branch, we will soon need to start branching R4E in order to compile
> with the updated Mylyn Versions.
>
> Since the code participating in the 0.7 release is more stable (e.g.
> less activity) I am wondering if it would be more convenient to move
> the code participating in 0.7 to a branch so the current activities
> with versions and reviews could continue updates of the API and
> implementation from the HEAD.
>
> How is this normally handled e.g. with other Mylyn projects ?
>
> /Alvaro
> _______________________________________________
> mylyn-versions-dev mailing list
> mylyn-versions-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/mylyn-versions-dev
>
--
Steffen Pingel
Committer, http://eclipse.org/mylyn
Senior Developer, http://tasktop.com
