+1 for a different JIRA system.
I believe that is the only way we can support an independent release cycle.

Rajith


On Thu, May 23, 2013 at 2:36 PM, Rob Godfrey <[email protected]>wrote:

> On 23 May 2013 20:24, Justin Ross <[email protected]> wrote:
>
> > This is great news!
> >
> > On Thu, May 23, 2013 at 11:07 AM, Robbie Gemmell
> > <[email protected]> wrote:
> > > Hi all,
> > [snip]
> > > In keeping with prior discussion of making the project structure more
> > > component-based, a couple of things we would like to do:
> > >
> > > - Create an area in svn, located alongside the proton directory, e.g:
> > > http://svn.apache.org/repos/asf/qpid/jms
> >
> > Perfect, IMO.
> >
> > > - Request creation of a JIRA project, e.g QPIDJMS, inititally for use
> > > relating to the new client but perhaps eventually serving for all QPID
> > JMS
> > > related components.
> >
> > Out of curiosity, why do you suggest a distinct jira instance (versus
> > using a jira component)?  I don't have a strong preference either way.
> >
>
> So for me there's a couple of reasons.  Most importantly the existing JIRA
> system is full of JIRAs for the existing client(s) which will make it very
> difficult to distinguish JIRAs for the new component from JIRAs relating to
> the older client libraries.  Within the context of a "QPID" JIRA system
> trying define components for "JMS client for AMQP 0-8/9/10", "JMS client
> for AMQP 1-0 not build on proton", and "JMS AMQP 1-0 client based on
> proton" such that people don't get confused may be difficult.  Secondly
> we'll definitely be using a different release schedule / version numbering
> from the existing components.  Once we sort out the components better I'd
> be fine with moving the older clients into the QPIDJMS jira/directory and
> we can tailor the component names to reduce any likelihood of confusion.
>
> -- Rob
>
>
> >
> > Justin
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >
> >
>

Reply via email to