Okay. Let's look at this in more detail: 1. major features like python and xml-schema or similar -> should get back into a primary place, e.g. own cluster for python maybe own cluster for xml-schema (could be consolidated with other xml-tooling). 2. single / simple feature modules from contrib -> vote if they should get directly promoted to default NetBeans or kept separate. For me this looks like a case by case decision.
If we want to have the code at Apache I would assume we want to ship it as well. On the other hand I like the idea of having something like incubating modules, which can be accessed via a special update center... Once they are mature enough we just ship the code... Not sure how this may end up in the actual repository structure, but special clusters seem to be a good idea. -Sven On Thu, Feb 13, 2020 at 7:34 PM Jesse Glick <typr...@gmail.com> wrote: > On Thu, Feb 13, 2020 at 11:27 AM Sven Reimers <sven.reim...@gmail.com> > wrote: > > I would assume that all things we pick up from the remaining stuff will > end > > up in the main NetBeans repository > > OK, in that case I guess they would be dumped in > `nbbuild/cluster.properties#nb.cluster.betauc` until someone decides > to promote them? (And fold the contents of `nb.cluster.experimental` > into that? I am not sure what the real distinction is.) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org > For additional commands, e-mail: dev-h...@netbeans.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > -- Sven Reimers * Java Champion * Apache NetBeans PMC: http://netbeans.apache.org * JUG Leader JUG Bodensee: https://www.meetup.com/JUG-Bodensee * Duke's Choice Award Winner 2009 & 2018 * LinkedIn: http://www.linkedin.com/in/svenreimers