[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
I'd say make a branch for 2.1 maintenance whenever one of us starts doing development that shouldn't go in it (I'm not yet).
That is, something that isn't bug fixes and improvements to existing stuff, in my opinion.
...Beth
Beth Tibbitts (859) 243-4981 (TL 545-4981)
High Productivity Tools / Parallel Tools http://eclipse.org/ptp
IBM T.J.Watson Research Center
Mailing Address: IBM Corp., 745 West New Circle Road, Lexington, KY 40511
Greg Watson ---12/03/2008 11:05:37 AM---Hi all,
Greg Watson <g.watson@xxxxxxxxxxxx>
Sent by: ptp-dev-bounces@xxxxxxxxxxx
12/03/2008 11:04 AM
Please respond to
Parallel Tools Platform general developers <ptp-dev@xxxxxxxxxxx> |
|
|
Hi all,
I need some advice on branches. Currently HEAD is the continuation of
2.1.0. At some point we need to create a 2.1 branch so that ongoing
development for 2.2 (or whatever) will not go into a 2.1.1 release.
Any suggestions when should I do that? It does complicate things for
developers because some fixes have to be checked into to places.
Greg
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev


