[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [eclipse.org-planning-council] Exception for Jubula project to be added late to Indigo build
|
+1
Adrian.
> -----Original Message-----
> From: eclipse.org-planning-council-bounces@xxxxxxxxxxx
> [mailto:eclipse.org-planning-council-bounces@xxxxxxxxxxx] On Behalf Of
> Achim Lörke
> Sent: jeudi 28 avril 2011 19:18
> To: eclipse.org-planning-council
> Cc: Zeb Ford-Reitz; Markus Tiede
> Subject: [eclipse.org-planning-council] Exception for Jubula project to
> be added late to Indigo build
>
>
> Hi all,
>
> sorry to bother you and it's kind of embarrassing but we need to ask
> for an Exception to be added (very) late to the build process.
>
> We've been working on making Jubula release train compliant and just
> realized that we missed a crucial step in the build, namely the
> aggregation build.
>
> This was uncovered during a meeting with Markus Knauer where we talked
> about contributing automated tests to the EPP. To make this tests
> widely usable it is necessary for Jubula to be part of Indigo.
>
> The build and all other requirements needed for M7 are done/fixed.
>
> We will write and maintain a checklist (on the Eclipse wiki) from our
> experience with joining the releases train which contains the
> necessary steps and persons involved in the process.
>
> Thanks
>
> Achim
>
> P.S.: I vote +1 for the exception ;-)
>
>
>
>
> --------------------------------------------------------
> BREDEX GmbH
> Mauernstr. 33
> 38100 Braunschweig
>
> Tel.: +49-531-24330-0
> Fax: +49-531-24330-99
> http: www.bredex.de
>
> Geschäftsführer: Hans-J. Brede, Achim Lörke, Ulrich Obst
> Amtsgericht Braunschweig HRB 2450
>
> _______________________________________________
> eclipse.org-planning-council mailing list
> eclipse.org-planning-council@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council
>
> IMPORTANT: Membership in this list is generated by processes internal
> to the Eclipse Foundation. To be permanently removed from this list,
> you must contact emo@xxxxxxxxxxx to request removal.
