On Fri, Aug 14, 2009 at 11:22 AM, Werner Punz<werner.p...@gmail.com> wrote: > Matthias Wessendorf schrieb: >> >> On Fri, Aug 14, 2009 at 11:04 AM, Werner Punz<werner.p...@gmail.com> >> wrote: >>> >>> Werner Punz schrieb: >>>> >>>> Hello everyone while I am preparing my initial commit I noticed >>>> following. >>>> We have a subproject for extension-extval but nothing more in this >>>> regard. >>>> Which means since I cannot open my own subproject in jira I am somehow >>>> blocked. >>>> >>>> Wouldnt it be better to have the project itself reside under extensions >>>> and then have different modules for extval, groovy etc.? >>>> >>>> >>> Ok Gerhard just gave me the explanation, it has something to do with the >>> release management. >> >> I think that in Trinidad it pretty much works well. We have plugin >> releases >> and core releases. With different release notes. Not sure what he means. >> Perhaps he could jump in ?! >> > Later, he is overloaded anyway, the question is submodules which means no > vote I assume, or subproject which means new vote. > In either case I dont think I can submit my code until all this is resolved.
Just saw your vote - ok let's wait for the outcome before committing - to be safe. I think that the entire community has to (kinda) approve such a new subproject, so thanks for triggering the vote. On the JIRA: I don't care that much if we have a new jira project or just a new component under a generic extensions project. But it is not the case that release mgmt is not possible in such a _mixed_ env (-> Trinidad) -M > > Werner > > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
