[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [mylyn-dev] R4E intent to join Indigo
|
Hi,
one of the pre-requisites for participation is to provide signed
artifacts. Since R4E is not included in Mylyn weekly builds I would
suggest that you request a separate Hudson build job for R4E that
signs artifacts and publishes to a separate repository, e.g. under
http://download.eclipse.org/reviews/r4e/juno/ .
We'll then need to request an aggregator file like this one
http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.juno.build/mylyn.b3aggrcon?view=markup&revision=1.5&root=Callisto
to contribute the published R4E artifacts to the train. To manage that
someone from the R4E team would need to obtain commit rights for the
callisto project (it's a simple process).
Steffen
On Wed, Oct 12, 2011 at 12:29 AM, alvaro sanchez <alvsan09@xxxxxxxxx> wrote:
>
> Upps, my mistake !
>
> For sure I meant to join the JUNO release train.
>
> Thanks for pointing this out,
>
> /Alvaro
>
>
> On Tue, Oct 11, 2011 at 4:57 PM, Matthias Sohn
> <matthias.sohn@xxxxxxxxxxxxxx> wrote:
> > 2011/10/11 alvaro sanchez <alvsan09@xxxxxxxxx>
> >>
> >> Hi,
> >> The R4E team would like to state the intention to join the Indigo
> >> simultaneous release,
> >
> > I guess you meant the Juno release train ? Indigo already shipped SR1 ...
> > According to [1] joining the release train must happen until M4.
> > [1] http://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements#State_intent_early
> > --
> > Matthias
> > _______________________________________________
> > mylyn-dev mailing list
> > mylyn-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/mylyn-dev
> >
> >
> _______________________________________________
> mylyn-dev mailing list
> mylyn-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mylyn-dev
--
Steffen Pingel
Committer, http://eclipse.org/mylyn
Senior Developer, http://tasktop.com
