|[eclipse.org-architecture-council] [Bug 344041] New: [EDP] Yearly reviews required|
https://bugs.eclipse.org/bugs/show_bug.cgi?id=344041 Product/Component: Community / Architecture Council Summary: [EDP] Yearly reviews required Classification: Eclipse Foundation Product: Community Version: unspecified Platform: PC URL: http://www.eclipse.org/org/documents/Eclipse%20BYLAWS% 202008_07_24%20Final.pdf OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: Architecture Council AssignedTo: eclipse.org-architecture-council@xxxxxxxxxxx ReportedBy: wayne@xxxxxxxxxxx Blocks: 342328 A project needs to do either a release, restructuring, or continuation review every year. The only exception is that permanent incubator projects are not required to have reviews of any kind. We need do a better job of policing this... Maybe we should take this opportunity to require that a projects (with the exception of permanent incubators) must do a *release* every year. From David Williams: My thoughts are it might be a bit much to _require_ a release every year ... seems there'd be so many qualifications (e.g. initial release might take 15 months .. then to align with yearly release the next one might take 18 months, etc.). But, perhaps the "intent" could be better codified with wording (around section 6.3) such as "... the expectation is that a Project will release once per year. If they do not, the projects PMC should ask for a formal continuation review to clarify what the plan is to get to a release". Or similar. -- Configure bugmail: https://bugs.eclipse.org/bugs/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
Back to the top