|Re: [eclipse-dev] IMPORTANT NOTE: Re: Eclipse Photon RC3 reminders - contributions should go to R4_8_maintenance branch|
Here are the logs generated just now.
There are some changes went in master only. Please cherry pick them onto R4_8_maintenance branch
Thanks and Regards,
Sravan Kumar Lakkimsetti
IBM India Pvt Ltd,
Embassy Golf Links Business Park, D Block,
Off Indiranagar-Kormangla Inner Ring Road,
Bangalore - 560071, India
From:Daniel Megert [mailto:daniel_megert@xxxxxxxxxx]
Sent: Sunday, May 27, 2018 8:37 PM
To: General development mailing list of the Eclipse project. <eclipse-dev@xxxxxxxxxxx>; Sravan K Lakkimsetti <sravankumarl@xxxxxxxxxx>
Subject: IMPORTANT NOTE: Re: [eclipse-dev] Eclipse Photon RC3 reminders - contributions should go to R4_8_maintenance branch
As outline below, all work for RC3 and beyond for 4.8 must go into the R4_8_maintenance branch.
Unfortunately, several commits went into master during the freeze period (blaming myself too), which means they are not in R4_8_maintenance branch.
If you know of such changes, please merge them into R4_8_maintenance branch.
Sravan, can you produce a diff report for all repositories, so that we don't miss any changes?
"Sravan K Lakkimsetti" ---25.05.2018 16:18:28---Hi,
From: "Sravan K Lakkimsetti" <sravankumarl@xxxxxxxxxx>
To: "Eclipse platform release engineering list." <platform-releng-dev@xxxxxxxxxxx>, platform-dev@xxxxxxxxxxx, "General development mailing list of the Eclipse project." <eclipse-dev@xxxxxxxxxxx>, equinox-dev@xxxxxxxxxxx
Date: 25.05.2018 16:18
Subject: [eclipse-dev] Eclipse Photon RC3 reminders - contributions should go to R4_8_maintenance branch
Sent by: eclipse-dev-bounces@xxxxxxxxxxx
Eclipse Photon RC3 is next week with a goal to deliver on June 01, 2017.
Please Note: All Contributions towards 4.8 should go to R4_8_maintenance branch. I-build will be done from this branch from now. We will open master for 4.9 development shortly.
The build schedule has been updated and can be downloaded from here. Freeze plan can read here.
- Fix approval: Two additional committers and a project lead must +1 your bug report (3 people who are not the one making the change).
- Notification requirements: Announce bug numbers of intended non-doc changes to platform-releng-dev@xxxxxxxxxxxmailing list.
Back to the top