Re: [cross-project-issues-dev] Ready for Luna (M1) aggregation ... and S

[David M Williams <david_williams@xxxxxxxxxx>]

What I typically do, is follow the 'dev
list' of the projects we rely on. There, most projects announce where particular
builds or repos are and when ready.  And, if not, you can ask there.
Such as for Eclipse, we always announce on several lists, one being 'eclipse-dev'
 

http://dev.eclipse.org/mhonarc/lists/eclipse-dev/msg09633.html

Orbit is similar, 
http://dev.eclipse.org/mhonarc/lists/orbit-dev/msg03447.html
(though admittedly, there you actually
have to look at the download page, to find the repository name ... but
there is a very predictable pattern). 

Occasionally, we "communicate"
with pre-req projects via bugzilla. For example, we in Platform do that
with EMF, since there is a subset of EMF that we in platform 
need to be "stable", before
the rest of EMF is (you know, we have one of the special relationships
where we depend on them, and they depend on us :) ... yet we are +0 and
they are +1, as a whole. 
For examples, see 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=414969
https://bugs.eclipse.org/bugs/show_bug.cgi?id=414968

Ideally, it is best not to wait until
the "final" build to build against ... but to occasionally "move
up" to a weekly I-build, for those projects that provide them, since
most projects know to make few changes as they near a milestone, so you
can get a "sneak peek" if there will be any surprises in the
final milestone build. 

Hope that helps, perhaps others have
other tips? 





From:      
 Igor Fedorenko <ifedorenko@xxxxxxxxxxxx>
To:      
 cross-project-issues-dev@xxxxxxxxxxx,

Date:      
 08/14/2013 12:33 PM
Subject:    
   Re: [cross-project-issues-dev]
Ready for Luna (M1) aggregation ... and SR1 reminders
Sent by:    
   cross-project-issues-dev-bounces@xxxxxxxxxxx

---

Can you elaborate? Using m2e as an example, what repositories
am I
supposed to use to resolve jdt, xml editor and emf dependencies needed
to build m2e Luna M1?

--
Regards,
Igor

On 2013-08-14 7:33 PM, David M Williams wrote:
> Nope. If you need that ... sounds like you are doing something wrong
:)
>
>
>
>
> From: Marcel Bruch <marcel.bruch@xxxxxxxxxxxxxx>
> To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>,
> Date: 08/14/2013 11:30 AM
> Subject: Re: [cross-project-issues-dev] Ready for Luna (M1) aggregation
> ...        and SR1 reminders
> Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
> ------------------------------------------------------------------------
>
>
>
> Hi David,
>
> is there any chance we can get
> _http://download.eclipse.org/releases/luna/_populated with the
> platform+jdt before m1?
>
> Thanks,
> Marcel
>
>
> On Aug 14, 2013, at 5:04 PM, David M Williams
> <_david_williams@xxxxxx.com_ <mailto:david_williams@xxxxxxxxxx>>
wrote:
>
>  > Hi David,
>  > could you please update the corresponding google calendar?
>  > I've imported the linked iCal file, but can't find any
Luna
>  > milestones entries.
>  >
>  > Best regards,
>  > Dennis.
>
>
> I have updated the Google Calendar for the reset of this year (through
> Luna M4) ... you can see there is "overlap" between Kepler
SR1 and Luna
> M2 ... so please
> plan accordingly. _
> __https://www.google.com/calendar/embed?src="">
>
> I'll update the rest after Planning Council formally approves it.
>
> Our SR1 RC1 is coming up soon. While it is considered a "warm-up"
please
> make sure your latest service contributions are "in" and
"working",
> since, shortly after that we have a pretty short runway to the final
SR1. _
> __http://wiki.eclipse.org/Kepler/Simultaneous_Release_Plan#SR1_
>
>
> Thanks,
>
> _______________________________________________
> cross-project-issues-dev mailing list_
> __cross-project-issues-dev@eclipse.org_
> <mailto: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
>
>
>
> _______________________________________________
> 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