You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by James Strachan <ja...@gmail.com> on 2007/02/27 11:50:36 UTC
moving JIRA issues for CMS and NMS...
To make it easier to tie together JIRAs and releases of CMS and NMS
with the release notes, I've done some JIRA refactoring so now all of
the issues assigned against CMS and NMS in the ACTIVEMQ project are
now moved into their respective JIRA projects...
https://issues.apache.org/activemq/browse/AMQNET
https://issues.apache.org/activemq/browse/AMQCPP
If anyone finds any old lingering issues which purely relate to CMS or
NMS its pretty easy to move them (or bulk edit a number of them).
Nathan/Tim I wonder if you could do a quick review of the resolved
issues with no Fixed Versions in the CMS JIRA and update them please?
--
James
-------
http://radio.weblogs.com/0112098/
Re: moving JIRA issues for CMS and NMS...
Posted by James Strachan <ja...@gmail.com>.
On 2/27/07, Nathan Mittler <na...@gmail.com> wrote:
> No worries :)
>
> Sure that would be fine - I'll cook something up in JIRA.
Great thanks!
--
James
-------
http://radio.weblogs.com/0112098/
Re: moving JIRA issues for CMS and NMS...
Posted by Nathan Mittler <na...@gmail.com>.
No worries :)
Sure that would be fine - I'll cook something up in JIRA.
On 2/27/07, James Strachan <ja...@gmail.com> wrote:
>
> On 2/27/07, Nathan Mittler <na...@gmail.com> wrote:
> > The only trick is that the C++ issues are not for the activemq-cpp
> client,
> > but rather the other c++ clients that have been donated by various
> groups.
> >
> > Not sure that Tim and I have the bandwidth to support those projects in
> > addition to activemq-cpp ... and with full openwire support days to
> weeks
> > away, I'm not sure we need to. Perhaps we should just close them all as
> > "Won't Fix". Does that seem reasonable?
>
> Doh! Sorry, I forgot about that. I figured we might as well keep all
> C++ related issues in the same JIRA project for simplicity - but by
> all means leave/ignore stuff thats not activemq-cpp related.
>
> I guess creating components within the ActiveMQ C++ JIRA project for
> the exact client they belong to would make sense - does that sound OK
> with you? You can then choose which issues are gonna get fixed in what
> release etc.
>
> --
>
> James
> -------
> http://radio.weblogs.com/0112098/
>
Re: moving JIRA issues for CMS and NMS...
Posted by James Strachan <ja...@gmail.com>.
On 2/27/07, Nathan Mittler <na...@gmail.com> wrote:
> The only trick is that the C++ issues are not for the activemq-cpp client,
> but rather the other c++ clients that have been donated by various groups.
>
> Not sure that Tim and I have the bandwidth to support those projects in
> addition to activemq-cpp ... and with full openwire support days to weeks
> away, I'm not sure we need to. Perhaps we should just close them all as
> "Won't Fix". Does that seem reasonable?
Doh! Sorry, I forgot about that. I figured we might as well keep all
C++ related issues in the same JIRA project for simplicity - but by
all means leave/ignore stuff thats not activemq-cpp related.
I guess creating components within the ActiveMQ C++ JIRA project for
the exact client they belong to would make sense - does that sound OK
with you? You can then choose which issues are gonna get fixed in what
release etc.
--
James
-------
http://radio.weblogs.com/0112098/
Re: moving JIRA issues for CMS and NMS...
Posted by Nathan Mittler <na...@gmail.com>.
The only trick is that the C++ issues are not for the activemq-cpp client,
but rather the other c++ clients that have been donated by various groups.
Not sure that Tim and I have the bandwidth to support those projects in
addition to activemq-cpp ... and with full openwire support days to weeks
away, I'm not sure we need to. Perhaps we should just close them all as
"Won't Fix". Does that seem reasonable?
On 2/27/07, James Strachan <ja...@gmail.com> wrote:
>
> To make it easier to tie together JIRAs and releases of CMS and NMS
> with the release notes, I've done some JIRA refactoring so now all of
> the issues assigned against CMS and NMS in the ACTIVEMQ project are
> now moved into their respective JIRA projects...
>
> https://issues.apache.org/activemq/browse/AMQNET
> https://issues.apache.org/activemq/browse/AMQCPP
>
> If anyone finds any old lingering issues which purely relate to CMS or
> NMS its pretty easy to move them (or bulk edit a number of them).
>
> Nathan/Tim I wonder if you could do a quick review of the resolved
> issues with no Fixed Versions in the CMS JIRA and update them please?
> --
>
> James
> -------
> http://radio.weblogs.com/0112098/
>