Hi, After having had discussions on ESE about how the nebula project can align itself to the release and incubation rules of the Eclipse Foundation.
Let me summarize the current situation: a) Only a (sub-)project can do a release! If we keep the current structure this means that we can only do a release if all Widget-Owners agree that their code is stable enough for a release! b) Only a (sub-)project can be in incubation! If we keep the current structure this means that all widgets are in incubation or none is which is not true when we look at widgets like Gallery, Grid who are quite stable c) Dormant. Only a (sub-)project can get into a dormant state! If we keep the current structure this means that we would all together get into dormant if we only want to have one widget (CTreeTable comes to my mind sorry Jeremy) to become dormant to indicate the user that there's currently no active development going on. d) We are afraid of doing 1.0 releases of stable widgets like PGroup, PShelf, Grid, ... because it stops us from doing breaking API changes. We don't need to be afraid about this. I think if we really need to break the API contract (we should do so though with a good reason) we need to switch to version 2.0 and continue there only doing bugfixes in 1.x. So Nebula-Widget(Subproject)-Leads and Technology-PMC now its your turn to comment on: a) Every *single* widget is transformed into a subproject. So it can follow its own release cycle, incubation state, committer election, ... . b) How can we the Nebula-Project-Leads and the Technology PMC ensure that the overhead for the current widgets is as easy as possible. For widgets like our nebula ones the subproject process is too heavy weight IMHO (at least for the existing ones). c) Should we start with widgets currently proposed at nebula with this process? Rich Text Control: ------------------ https://bugs.eclipse.org/bugs/show_bug.cgi?id=255340 RadioGroup/RadioItem: --------------------- https://bugs.eclipse.org/bugs/show_bug.cgi?id=249060 And then step by step move the existing ones to this new structure. d) Open up our own IRC as a fast communication channel between committers, project leads, ... ? I would have been in need of this last week where the E4 asked me to get a tagged version of the Gallery to setup a build (well Nicolas infact there now exist a build for your [1] :-) Thanks for your attention and your feedback and the time you all invest into the cool nebula controls! Tom [1]http://download.eclipse.org/e4/downloads/drops/I20081120-1930/index.html _______________________________________________ nebula-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/nebula-dev
