| [jdt-core-dev] [eclipse-dev] Branching the 2.1 stream |
Branch R2_1_maintenance created, it is rooted at version v_312 (R2_1 +
extra tuning for SR2 JIT failures).
Our latest HEAD contents is only meant for 2.2, and we may want to backport
a few fixes back to R2_1_maintenance branch.
----- Forwarded by Philippe P Mulet/France/IBM on 04/04/2003 05:55 PM -----
Dean
Roberts/Ottawa/IBM To: eclipse-dev@xxxxxxxxxxx
@IBMCA cc:
Sent by: Subject: [eclipse-dev] Branching the 2.1 stream
eclipse-dev-admin@
eclipse.org
04/04/2003 05:49
PM
Please respond to
eclipse-dev
Hi teams,
Although no firm dates or plans have been speculated for a 2.1.1 release I
think it would be naive to pretend there will not be one.
Unlike 2.0 where the RelEng team branched all the CVS projects using a
bogus name for the branch we will do better this time.
1) I think each individual team should branch their own code from 2.1 when
they actually have code that needs to go into a 2.1.1 release. This will
let us see who has 2.1.1 code.
2) The name of the branch should be
R2_1_maintenance.
(The mistake we made last time was calling the branch R2_0_1. This was
fine for 2.0.1 development but looked really odd for 2.0.2 development <g>)
If anybody has any comments or dissenting opinions please let us know.
Thanks
...Dean...