> Nevertheless I wonder on what basis statements like "PMC must approve 
all feature work and API changes.? are made. Is there a 
top-level-project-specific ramp down plan that covers this kind of things?

No. Each (top-level) project has its own rules. Some still allow feature 
work during ramp-down without approvals.

Dani



From:   Alexander Nyßen <[email protected]>
To:     Cross project issues <[email protected]>
Date:   04.05.2015 16:00
Subject:        Re: [cross-project-issues-dev] Ramp-down policy for Mars
Sent by:        [email protected]



Thanks Dani,

indeed that helps. 

Nevertheless I wonder on what basis statements like "PMC must approve all 
feature work and API changes.? are made. Is there a 
top-level-project-specific ramp down plan that covers this kind of things?

Cheers
Alexander

Am 04.05.2015 um 15:25 schrieb Daniel Megert <[email protected]>:

Hi Alexander 

There is no cross-project ramp-down plan. If it helps, here is the endgame 
plan that the Eclipse top-level project follows: 
https://www.eclipse.org/eclipse/development/plans/freeze_plan_4_5.php 

Dani 



From:        Alexander Nyßen <[email protected]> 
To:        Cross project issues <[email protected]> 
Date:        04.05.2015 15:19 
Subject:        [cross-project-issues-dev] Ramp-down policy for Mars 
Sent by:        [email protected] 



As we are passing M7, I was wondering whether there is an official 
ramp-down policy all projects should follow (i.e. from when on changes 
will have to be reviewed by the project lead, PMC, etc.). I ran across 
these kinds of statements in old release plans but cannot find an 
up-to-date statement concerning it. Where would I have to look? 

Cheers 
Alexander 
-- 
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 
[email protected] 

itemis AG
Am Brambusch 15-24
44536 Lünen

Rechtlicher Hinweis:

Amtsgericht Dortmund, HRB 20621

Vorstand: Jens Wagener (Vors.), Wolfgang Neuhaus, Dr. Georg Pietrek, Jens 
Trompeter, Sebastian Neus

Aufsichtsrat: Prof. Dr. Burkhard Igel (Vors.), Michael Neuhaus, Jennifer 
Fiorentino


[attachment "signature.asc" deleted by Daniel Megert/Zurich/IBM] 
_______________________________________________
cross-project-issues-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe 
from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev 
_______________________________________________
cross-project-issues-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe 
from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

--
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 
[email protected] 

itemis AG
Am Brambusch 15-24
44536 Lünen

Rechtlicher Hinweis:

Amtsgericht Dortmund, HRB 20621

Vorstand: Jens Wagener (Vors.), Wolfgang Neuhaus, Dr. Georg Pietrek, Jens 
Trompeter, Sebastian Neus

Aufsichtsrat: Prof. Dr. Burkhard Igel (Vors.), Michael Neuhaus, Jennifer 
Fiorentino


[attachment "signature.asc" deleted by Daniel Megert/Zurich/IBM] 
_______________________________________________
cross-project-issues-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe 
from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Reply via email to