[sequoyah-dev] Fwd: [cross-project-issues-dev] Status and outlook for In

[Daniel Pastore <kpqb38@xxxxxxxxxxxx>]

Hi guys,

just following David Williams advice, this is an email to announce that since we had no bugfixes for Indigo SR2, Sequoyah will be using Indigo's SR1 build for the last release of the Indigo train.


Thanks all for the support! 
Any questions, suggestions and contributions are welcome at any time!

Best,

---------- Forwarded message ----------
From: David M Williams <david_williams@xxxxxxxxxx>
Date: Wed, Jan 18, 2012 at 18:55
Subject: Re: [cross-project-issues-dev] Status and outlook for Indigo SR2 RC1 warm-up build
To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Cc: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>, cross-project-issues-dev-bounces@xxxxxxxxxxx


No, if nothing changes, you do not need to change versions (in fact, best
not to!)

I know in the past this sometimes it has confusing to adopters ... when
versions do not change ...  that might be waiting for your next version ...
but I think a simple announcement on your dev list that your x.y.1 version
will be your contribution to Indigo SR2 suffices to clear that up.

Thanks,




From:   Daniel Pastore <kpqb38@xxxxxxxxxxxx>
To:     Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>,
Date:   01/18/2012 03:07 PM
Subject:        Re: [cross-project-issues-dev] Status and outlook for Indigo
           SR2 RC1 warm-up build
Sent by:        cross-project-issues-dev-bounces@xxxxxxxxxxx

Hi David,

Just a quick question: I've seen you kept our SR1 contribution for
Sequoyah, and as we are almost on maintenance, we don't have any bugfixes
for SR2. Do I *need* to generate another build, with a x.y.2 version or can
we keep this x.y.1, since the code will be the same?

And thanks for your quick help over all these warm-up weeks! :)

On Wed, Jan 18, 2012 at 17:58, David M Williams <david_williams@xxxxxxxxxx>
wrote:

 tick tock

 Here we are already at 3 PM on +3 day. Unless someone shouts "wait", I'll
 consider the updates for RC1 finished by 5 PM today (Eastern), and what
 ever build is current will then become our "maintenance" staging repo for
 RC1.

 http://download.eclipse.org/releases/maintenance/

 There are two contribution files that have disabled features or
 repositories ... riena being the largest omission ... last call! :)

 ep.b3aggrcon (see bug 362103)
 riena.b3aggrcon

 Markus tells me, in keeping with tradition, he will produce the EPP
 packages with the same spirit of "warm-up" (not moved to downloads, not
 mirrored, no official sign-off, but the maintainers (or, anyone) can
 still
 test from the EPP build site.

 In two short weeks we'll produce RC2 which overlaps with Juno M5! ... so,
 plan accordingly ... I'm sure we'll be keeping the build machine(s) warm
 that week.

 Indigo: http://wiki.eclipse.org/Indigo/Simultaneous_Release_Plan#SR2
 Juno: http://wiki.eclipse.org/Juno/Simultaneous_Release_Plan#Schedule


 Thanks,


 _______________________________________________
 cross-project-issues-dev mailing list
 cross-project-issues-dev@xxxxxxxxxxx
 https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



--
Thanks,

Daniel Pastore_______________________________________________

cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

-- 
Thanks,

Daniel Pastore
Sequoyah Team