[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [eclipse.org-planning-council] Eclipse Target Management to re-join Eclipse Photon Release for M6?
|
+1
Cheers,
-Martin
> Am 26.02.2018 um 18:08 schrieb Nick Boldt <nboldt@xxxxxxxxxx>:
>
> Greetings Eclipse Planning Council members,
>
> The Eclipse Target Management project has missed the M4 deadline, but would still like to participate in the Eclipse Photon release.
>
> As a new committer for TM, I've updated the RSE build so it runs against the latest Eclipse Photon 4.8 milestone bits [0].
>
> [0] https://git.eclipse.org/c/tm/org.eclipse.tm.git/tree/pom.xml#n19
>
> Here's what I sent to tm-dev last week:
>
> https://dev.eclipse.org/mhonarc/lists/tm-dev/msg01282.html
>
> The project's builds are currently in the aggregation (AFAICT they were not cleaned them out yet [1]), so the impact of this addition should be minimal - I just need to provide a new URL from which to aggregate the 2 RSE features. I believe this to be very low risk.
>
> [1] https://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/tree/tm.aggrcon
>
> I hereby ask the Eclipse Planning Council to grant the Eclipse TM project an exception to allow them to opt-in to participate in the Eclipse Photon release despite missing the deadline.
>
> Please signal your agreement by voting +1 on this thread.
>
> Thanks,
>
> --
> Nick Boldt
> Senior Software Engineer, RHCSA
> Productization Lead :: JBoss Tools & Dev Studio
> IM: @nickboldt / @nboldt / http://nick.divbyzero.com
>
> TRIED. TESTED. TRUSTED.
> @ @redhatnews Red Hat
>
>
> “The Only Thing That Is Constant Is Change” - Heraclitus
>
> _______________________________________________
> 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.