[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jdt-core-dev] 3.1 maintenance and beyond
|
It simply reflects priorities for the short term. HEAD will soon have
changes we do not want to push in 3.1.1, and this a way to protect our
3.1.1 development.
Of course, we will perform merges from 3.1.1 branch back to HEAD before we
start build 3.2 again, but until then we want to concentrate on 3.1.1.
Daniel
Megert/Zurich/IBM
@IBMCH To
Sent by: "Eclipse JDT Core developers list."
jdt-core-dev-boun <jdt-core-dev@xxxxxxxxxxx>
ces@xxxxxxxxxxx cc
Subject
06/29/2005 12:13 Re: [jdt-core-dev] 3.1 maintenance
PM and beyond
Please respond to
"Eclipse JDT Core
developers list."
>So if you are fixing a 3.1.1 defect, there is no need to merge it
>immediately in HEAD; and we should keep HEAD clean as much as we can.
This means we will not get the latest J Core fixes when self-hosting on 3.2
integration builds. Sounds strange to me.
Dani
Philippe P
Mulet/France/IBM@
IBMFR To
Sent by: jdt-core-dev@xxxxxxxxxxx
jdt-core-dev-boun cc
ces@xxxxxxxxxxx
Subject
[jdt-core-dev] 3.1 maintenance and
29.06.2005 10:19 beyond
Please respond to
"Eclipse JDT Core
developers list."
<jdt-core-dev@ecl
ipse.org>
While we are still debating what 3.2 will be about, we will focus on
maintenance in the R3_1_maintenance branch.
Once we make enough progress, we will merge all changes from
R3_1_maintenance back into HEAD.
So if you are fixing a 3.1.1 defect, there is no need to merge it
immediately in HEAD; and we should keep HEAD clean as much as we can.
Remember that 3.1.1 issues are controlled, and should be acknowledged by me
prior to releasing changes.
_______________________________________________
jdt-core-dev mailing list
jdt-core-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jdt-core-dev
_______________________________________________
jdt-core-dev mailing list
jdt-core-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jdt-core-dev
