I think that if this discussion is raised only because it's difficult to have a despot create the project in jira, then we may just want to have more despots. Changing the release process not because it's having an issue in itself seems wrong to me.
Like Arnaud, I also think it's a wee bit better to have a dedicated project when out of pre-release state. My 2 cents Le 3 sept. 2014 10:00, "Arnaud Héritier" <aherit...@codehaus.org> a écrit : > I would prefer to have a jira project per mojo when they are stable > AFAIK I'm always despot + jira administrator and can create projects if > you need but don't hesitate to ping me directly because I'm not reading all > mojo MLs threads > > > On Wed, Sep 3, 2014 at 9:39 AM, Anders Hammar <and...@hammar.net> wrote: > >> One problem is that the JIRA URL is on the produced mojo site, so >> creating the JIRA project after the release requires a new release to >> update the site. >> >> /Anders >> >> >> On Wed, Sep 3, 2014 at 9:31 AM, Dan Tran <dant...@gmail.com> wrote: >> >>> Correct >>> >>> -Dan >>> >>> >>> On Tuesday, September 2, 2014, Anders Hammar <and...@hammar.net> wrote: >>> >>>> Not sure what you mean. Do you want to make a 1.0 release without a >>>> mojo specific JIRA project? >>>> >>>> /Anders >>>> >>>> >>>> On Wed, Sep 3, 2014 at 8:29 AM, Dan Tran <dant...@gmail.com> wrote: >>>> >>>>> Currently in order for a component to become 1.0, it just have a Jira >>>>> project. So far we have a hard time getting depot to manage this >>>>> procedure. >>>>> >>>>> Could we just mangen it like the way Jenkins does with plugin? a >>>>> component id is just good enough >>>>> >>>>> Thanks >>>>> >>>>> -Dan >>>>> >>>>> >>>> >> >
