Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdt-papyrus.dev] Maintenance branches

Thanks, Camille.

I have made corresponding updates to the Oomph setup model to help people get started working with the Neon (master) and Mars-maintenance branches:

    https://bugs.eclipse.org/bugs/show_bug.cgi?id=470404

Cheers,

Christian




On Tue, Jun 16, 2015 at 5:37 AM, LETAVERNIER Camille <Camille.LETAVERNIER@xxxxxx> wrote:

Hi all,

 

 

I’ve created two new branches: one for the Mars Maintenance, ‘streams/1.1-maintenance’ (SR1, SR2...), and another one for the short-term RC4b, ‘bugs/470250-RC4b’

 

I will also set up the associated builds, and associate the current ‘master’ branch to the Neon builds.

 

Maybe we should also clean up some old builds on Hudson. I propose to remove the following:

 

Complete Features:

-          Papyrus-Feature-DiagramSync

-          Papyrus-Feature-DiagramSync-Tests

-          Papyrus-Feature-DirectEditor

-          Papyrus-Feature-DirectEditor-Tests

-          Papyrus-Feature-Mars-RelationshipInModelExplorer

-          Papyrus-Feature-Mars-RelationshipInModelExplorer-Tests

-          Papyrus-Feature-Master-Filter

-          Papyrus-Feature-Master-Filter-Tests

 

Deprecated builds:

-          PublishTestFramework

-          PublishTestFramework-luna

 

Never used builds:

-          Papyrus-Master-Javadoc

-          Papyrus-Master-MavenSite

 

Regarding the TestFramework, it is now part of the Developer Tools, for Mars+, and we don’t need it for Luna anymore.

 

If you want some of these builds to be retained, please comment quickly. Otherwise, I’ll remove them soon

 

 

Regards,
Camille



Back to the top