Re: [tm-dev] terminal repo

[Doug Schaefer <dschaefer@xxxxxxx>]

My only question is why inflict that pain on the community. Everyone else
is working towards shipping the entire stack from Mars, not picking and
choosing releases. You could create your own builds that do that (like we
have with CDT and the different targets for each platform release).

Doug

On 2015-06-03, 10:12 AM, "Oberhuber, Martin"
<Martin.Oberhuber@xxxxxxxxxxxxx> wrote:

>Hi Greg,
>
>The reason for splitting was that o.e.remote still doesn't build on
>Eclipse 3.8 (my contribution supports 4.3 but not 3.8).
>But we want the Terminal to also work on 3.8 at least for now.
>
>I would suggest releasing mars from the 4.0-maintenance branch -- this
>allows us to stabilize for mars without blocking development in master.
>
>I've created a "terminal-4.0-maintenance" Hudson Job for you:
>https://hudson.eclipse.org/tm/job/terminal-4.0-maintenance/
>It's output is deployed to this repo:
>http://download.eclipse.org/tm/terminal/builds/mars/nightly
>
>So you now have both options --
>a) copy the builds/mars/nightly to builds/mars/milestones and register
>that for the simrel RC3, if you want to release from the branch. Or
>b) copy the builds/development/nightly to builds/development/milestones,
>and  if you want to release from master.
>    The nightly is already set up as a composite, and composites under
>another composite work just fine.
>
>HTH, let me know if you have any more questions.
>
>Thanks,
>Martin
>--
>Martin Oberhuber, SMTS / Product Owner - Development Tools, Wind River
>direct +43.662.457915.85  fax +43.662.457915.6
>
>
>-----Original Message-----
>From: tm-dev-bounces@xxxxxxxxxxx [mailto:tm-dev-bounces@xxxxxxxxxxx] On
>Behalf Of Greg Watson
>Sent: Wednesday, June 03, 2015 3:43 AM
>To: TM project developer discussions
>Subject: [tm-dev] terminal repo
>
>It looks the terminal build has been split into two parts, remote and
>everything else. Can whoever did this explain how they are planning to
>include both these in the 4.0milestones update site so they can be picked
>up by the simrel build? I need this sorted out right now so that I can
>get changes into the RC3 build.
>
>Greg
>_______________________________________________
>tm-dev mailing list
>tm-dev@xxxxxxxxxxx
>To change your delivery options, retrieve your password, or unsubscribe
>from this list, visit https://dev.eclipse.org/mailman/listinfo/tm-dev
>_______________________________________________
>tm-dev mailing list
>tm-dev@xxxxxxxxxxx
>To change your delivery options, retrieve your password, or unsubscribe
>from this list, visit
>https://dev.eclipse.org/mailman/listinfo/tm-dev