RE: [platform-releng-dev] R3_2_maintenance branch created

[Kim Moir <Kim_Moir@xxxxxxxxxx>]

Hi Walter

I usually fix bugs in HEAD and then
compare the branches and apply the fixes in the maintenance branch if required.
Of course, not all bugs fixed in HEAD need to be ported back to the maintenance
branch if they are not going to be fixed for 3.2.

Kim

"Walter Harley" <wharley@xxxxxxx>
Sent by: platform-releng-dev-bounces@xxxxxxxxxxx

06/05/2006 06:11 PM

Please respond to
"Eclipse platform release engineering list."

To	"Eclipse platform release engineering list." <platform-releng-dev@xxxxxxxxxxx>
cc
Subject	RE: [platform-releng-dev] R3_2_maintenance branch created

Thanks, Kim!
 
Is the Eclipse norm for bugs to
be fixed on the maintenance branch and then merged into HEAD, or vice versa?
 (I know either one is possible, just wondering which is more typical
for folks here.)
 
  -Walter

---

From: platform-releng-dev-bounces@xxxxxxxxxxx
[mailto:platform-releng-dev-bounces@xxxxxxxxxxx] On Behalf Of Kim
Moir
Sent: Monday, June 05, 2006 2:31 PM
To: platform-releng-dev@xxxxxxxxxxx
Subject: [platform-releng-dev] R3_2_maintenance branch created


A R3_2_maintenance branch of the org.eclipse.releng project has been created.
 All further 3.2 development will continue in this branch.  

Versions of projects contributed to the I20060605-1430 build have been
rtagged with I20060605-1430 to allow teams to use a single tag as a branch
point for further 3.2 development.   

Maintenance builds toward 3.2 will be on a request basis.

HEAD is now open for 3.3 development.  Nightly builds will run from
HEAD starting tonight June 6 at 00:10. 

Integration builds toward 3.3 will begin Tuesday June 13 at 8am ET.

http://www.eclipse.org/eclipse/platform-releng/buildSchedule.html

Please get in touch with friendly neighbourhood releng team if you have
any questions. 

Kim
_______________________________________________________________________
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries
 and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted
 and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.
_______________________________________________
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-releng-dev