| Re: [tm-dev] TM Terminal 3.6 maintenance |
|
Hi Greg, It’s done, but note that I had to name the branch “TM_3.6_maintenance”, following the example of “TM_3.5_maintenance”, as there is a “R3_6_maintenance” branch
already, but this one is more than 5 years old. The same is true for “R3_5_maintenance”. Guess it had been the reason to switch to the “TM_<n>_maintenance” schema. The corresponding Jenkins job is “tm-3.6-maintenance”. See
https://hudson.eclipse.org/tm/job/tm-3.6-maintenance/. No auto publishing of the resulting P2 repository (same as for “tm-3.5-maintenance”). If you desire to have auto publishing for the maintenance
builds in place, please talk to Anna, who is maintaining the pom files for the TM project. Best regards, Uwe
J From: tm-dev-bounces@xxxxxxxxxxx [mailto:tm-dev-bounces@xxxxxxxxxxx]
On Behalf Of Greg Watson Hi Uwe, Sounds fine to me. Regards, Greg On Jul 2, 2014, at 3:28 AM, Stieber, Uwe <Uwe.Stieber@xxxxxxxxxxxxx> wrote:
Hi Greg, I have some bugfixes and small enhancements in the pipe for the TM Terminal 3.6 stream. For the moment, there is only a tag (R3_6) but no branch. If you don’t object I will
go and create the “R3_6_maintenance” branch based on your tag and will cherry pick the fixes from the master branch. The master will lead to TM Terminal 3.7. Once it is time to provide drops for the Luna service release, we definitely need to deliver a new
TM Terminal 3.6 build from the maintenance branch to that Luna service release. Any comments? Thanks, Best regards, Uwe J _______________________________________________ |