Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse.org-planning-council] Can LDT join the Eclipse Oxygen Simultaneous Release?

I agree with others, the tools PMC should give the go ahead.  With that I have no issues including LDT in Oxygen.

Tom
 
 
 
----- Original message -----
From: Martin Lippert <mlippert@xxxxxxxxx>
Sent by: eclipse.org-planning-council-bounces@xxxxxxxxxxx
To: Eclipse Planning Council private list <eclipse.org-planning-council@xxxxxxxxxxx>
Cc:
Subject: Re: [eclipse.org-planning-council] Can LDT join the Eclipse Oxygen Simultaneous Release?
Date: Thu, Feb 9, 2017 3:33 AM
 
+1
I think the Tools PMC should be involved here.

Cheers,
-Martin


> Am 09.02.2017 um 08:32 schrieb Daniel Megert <daniel_megert@xxxxxxxxxx>:
>
> > I agree with Sam. Why define processes if they do not need to be followed?
>
> Same here.
>
> Dani
>
>
>
> From:        Alexander Nyßen <nyssen@xxxxxxxxx>
> To:        Eclipse Planning Council private list <eclipse.org-planning-council@xxxxxxxxxxx>
> Date:        09.02.2017 08:29
> Subject:        Re: [eclipse.org-planning-council] Can LDT join the Eclipse Oxygen        Simultaneous Release?
> Sent by:        eclipse.org-planning-council-bounces@xxxxxxxxxxx
>
>
>
> I agree with Sam. Why define processes if they do not need to be followed?
>
> Regards,
> Alexander
>
> Am 08.02.2017 um 23:03 schrieb Sam Davis <sam.davis@xxxxxxxxxxx>:
>
> GIven they are in M5 it seems better to me to include them, but if the process is for them to petition via their PMC for an exception I don't see why we shouldn't follow it. It would be nice to know they are paying enough attention to do that.
>
> Sam
>
>
> --
> Sam Davis
> Senior Software Engineer, Tasktop
> Committer, Eclipse Mylyn
> http://tasktop.com
>
> On Wed, Feb 8, 2017 at 1:34 PM, Wayne Beaton <wayne@xxxxxxxxxxx> wrote:
> Greetings Planning Council.
> I managed to connect with the Eclipse LDT project regarding their participation in the Eclipse Oxygen release. LDT was part of the Eclipse Mars and Eclipse Neon releases.
>
> I'm a little concerned that they did not respond to my numerous notes on cross-project-issues-dev. Either they weren't connected or weren't listening (neither of these scenarios are particularly comforting). It looks like they're paying attention now.
>
> Their aggregation file was never deactivated, so their bits are in M5. I believe that this means that there is actually more risk in excluding them.
>
>
> According to my understanding of the rules, since they missed the M4 deadline, they're supposed petition via their PMC for an exception to be included in the release.
>
> I started typing this note thinking that I'd ask for an opinion from the Planning Council regarding whether or not such a petition is necessary. While typing this note, it sort of morphed into a petition for an exception. I'm not a member of the Tools PMC, however, so I will defer to their representative and offer my humble apology if I've overstepped my bounds or have otherwise misrepresented their interests.
>
> So... the question is... Can LDT join the Eclipse Oxygen Simultaneous Release?
>
> I'd rather avoid lazy consensus, so your vote will be appreciated.
>
> Thanks,
>
> Wayne
>
>
>
> -------- Forwarded Message --------
> Subject:
> [cross-project-issues-dev] LDT participation to Oxygen
> Date:
> Tue, 7 Feb 2017 10:55:18 +0100
> From:
> Simon Bernard <sbernard@xxxxxxxxxxxxxxxxxx>
> Reply-To:
> Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
> To:
> Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
>
>
>
> Sry for the late declaration, if it's still possible, the LDT project will participate in the Eclipse Oxygen simultaneous release with an offset of +3.
>
> This will be with the 1.4.1 : https://projects.eclipse.org/projects/tools.ldt/releases/1.4.1
>
> Regards,
> Simon
>
>
> --
> Wayne Beaton
> @waynebeaton
> The Eclipse Foundation
> <ConvergeLogo_Transparent.png>
>
> _______________________________________________
> 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@eclipse.orgto request removal.
>
> _______________________________________________
> 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.
>
> --
> Dr. Alexander Nyßen
> Dipl.-Inform.
> Principal Engineer
>
> Telefon: +49 (0) 231 / 98 60-202
> Telefax: +49 (0) 231 / 98 60-211
> Mobil: +49 (0) 151 /  17396743
>
> http://www.itemis.de
> alexander.nyssen@xxxxxxxxx
>
> itemis AG
> Am Brambusch 15-24
> 44536 Lünen
>
> Rechtlicher Hinweis:
>
> Amtsgericht Dortmund, HRB 20621
>
> Vorstand: Jens Wagener (Vors.), Wolfgang Neuhaus
>
> Aufsichtsrat: Prof. Dr. Burkhard Igel (Vors.), Michael Neuhaus, Jennifer Fiorentino
>
>
> [attachment "signature.asc" deleted by Daniel Megert/Zurich/IBM] _______________________________________________
> 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.
>
>
> _______________________________________________
> 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.
>

_______________________________________________
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.
 


Back to the top