You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@karaf.apache.org by Andreas Pieber <an...@gmail.com> on 2011/04/22 23:25:49 UTC
[INFRA PROPOSAL] add "library upgrade" as issue type
Hey guys,
On most projects I'm working on we have an own issue type "library
upgrade". The problem is that some ppl are interested into what libs
are upgraded between two releases and if those are scattered between
tasks and improvements in the changelog they are typically hard to
find. Adding an own issue type collects them quite nicely in the
changelog and in addition no one have to think if an upgrade is a task
or an improvement ;)
WDYT? Kind regards,
Andreas
Re: [INFRA PROPOSAL] add "library upgrade" as issue type
Posted by Claus Ibsen <cl...@gmail.com>.
On Sat, Apr 23, 2011 at 9:22 AM, Guillaume Nodet <gn...@gmail.com> wrote:
> It is globally available now. Just try and let me know if you don't see it.
>
For SMX / Camel etc I only see the "standard" first 6 issue types.
If I select Karaf there is many new issue types (about 12-14 or so)
and Dependecy Update is the last one.
I also tried to log-out and log-in again to see if that would work.
Unfortunately not.
> On Sat, Apr 23, 2011 at 09:18, Claus Ibsen <cl...@gmail.com> wrote:
>> On Sat, Apr 23, 2011 at 8:35 AM, Guillaume Nodet <gn...@gmail.com> wrote:
>>> Looks like I've just done that.
>>> If you create a new issue, you should have a "Dependency upgrade" type now.
>>>
>>
>> Hi Guillaume.
>>
>> How did you do that? It would be nice to have that for SMX and Camel
>> as well, as we frequent upgrade libraries as well.
>>
>>
>>> On Sat, Apr 23, 2011 at 08:28, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
>>>> I have to check if I have permission to do that.
>>>>
>>>> I will let you know.
>>>>
>>>> Regards
>>>> JB
>>>>
>>>> On 04/23/2011 08:26 AM, Andreas Pieber wrote:
>>>>>
>>>>> Can someone of us do this (I have no admin tab in JIRA :( ) or should
>>>>> I create an issue at INFRA?
>>>>>
>>>>> Kind regards,
>>>>> Andreas
>>>>>
>>>>> On Sat, Apr 23, 2011 at 8:23 AM, Guillaume Nodet<gn...@gmail.com> wrote:
>>>>>>
>>>>>> It sounds like a good idea.
>>>>>>
>>>>>> On Fri, Apr 22, 2011 at 23:25, Andreas Pieber<an...@gmail.com> wrote:
>>>>>>>
>>>>>>> Hey guys,
>>>>>>>
>>>>>>> On most projects I'm working on we have an own issue type "library
>>>>>>> upgrade". The problem is that some ppl are interested into what libs
>>>>>>> are upgraded between two releases and if those are scattered between
>>>>>>> tasks and improvements in the changelog they are typically hard to
>>>>>>> find. Adding an own issue type collects them quite nicely in the
>>>>>>> changelog and in addition no one have to think if an upgrade is a task
>>>>>>> or an improvement ;)
>>>>>>>
>>>>>>> WDYT? Kind regards,
>>>>>>> Andreas
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Cheers,
>>>>>> Guillaume Nodet
>>>>>> ------------------------
>>>>>> Blog: http://gnodet.blogspot.com/
>>>>>> ------------------------
>>>>>> Open Source SOA
>>>>>> http://fusesource.com
>>>>>>
>>>>>> Connect at CamelOne May 24-26
>>>>>> The Open Source Integration Conference
>>>>>> http://camelone.com/
>>>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Cheers,
>>> Guillaume Nodet
>>> ------------------------
>>> Blog: http://gnodet.blogspot.com/
>>> ------------------------
>>> Open Source SOA
>>> http://fusesource.com
>>>
>>> Connect at CamelOne May 24-26
>>> The Open Source Integration Conference
>>> http://camelone.com/
>>>
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> FuseSource
>> Email: cibsen@fusesource.com
>> Web: http://fusesource.com
>> CamelOne 2011: http://fusesource.com/camelone2011/
>> Twitter: davsclaus
>> Blog: http://davsclaus.blogspot.com/
>> Author of Camel in Action: http://www.manning.com/ibsen/
>>
>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
>
> Connect at CamelOne May 24-26
> The Open Source Integration Conference
> http://camelone.com/
>
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
CamelOne 2011: http://fusesource.com/camelone2011/
Twitter: davsclaus
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
Re: [INFRA PROPOSAL] add "library upgrade" as issue type
Posted by Guillaume Nodet <gn...@gmail.com>.
It is globally available now. Just try and let me know if you don't see it.
On Sat, Apr 23, 2011 at 09:18, Claus Ibsen <cl...@gmail.com> wrote:
> On Sat, Apr 23, 2011 at 8:35 AM, Guillaume Nodet <gn...@gmail.com> wrote:
>> Looks like I've just done that.
>> If you create a new issue, you should have a "Dependency upgrade" type now.
>>
>
> Hi Guillaume.
>
> How did you do that? It would be nice to have that for SMX and Camel
> as well, as we frequent upgrade libraries as well.
>
>
>> On Sat, Apr 23, 2011 at 08:28, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
>>> I have to check if I have permission to do that.
>>>
>>> I will let you know.
>>>
>>> Regards
>>> JB
>>>
>>> On 04/23/2011 08:26 AM, Andreas Pieber wrote:
>>>>
>>>> Can someone of us do this (I have no admin tab in JIRA :( ) or should
>>>> I create an issue at INFRA?
>>>>
>>>> Kind regards,
>>>> Andreas
>>>>
>>>> On Sat, Apr 23, 2011 at 8:23 AM, Guillaume Nodet<gn...@gmail.com> wrote:
>>>>>
>>>>> It sounds like a good idea.
>>>>>
>>>>> On Fri, Apr 22, 2011 at 23:25, Andreas Pieber<an...@gmail.com> wrote:
>>>>>>
>>>>>> Hey guys,
>>>>>>
>>>>>> On most projects I'm working on we have an own issue type "library
>>>>>> upgrade". The problem is that some ppl are interested into what libs
>>>>>> are upgraded between two releases and if those are scattered between
>>>>>> tasks and improvements in the changelog they are typically hard to
>>>>>> find. Adding an own issue type collects them quite nicely in the
>>>>>> changelog and in addition no one have to think if an upgrade is a task
>>>>>> or an improvement ;)
>>>>>>
>>>>>> WDYT? Kind regards,
>>>>>> Andreas
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Cheers,
>>>>> Guillaume Nodet
>>>>> ------------------------
>>>>> Blog: http://gnodet.blogspot.com/
>>>>> ------------------------
>>>>> Open Source SOA
>>>>> http://fusesource.com
>>>>>
>>>>> Connect at CamelOne May 24-26
>>>>> The Open Source Integration Conference
>>>>> http://camelone.com/
>>>>>
>>>
>>
>>
>>
>> --
>> Cheers,
>> Guillaume Nodet
>> ------------------------
>> Blog: http://gnodet.blogspot.com/
>> ------------------------
>> Open Source SOA
>> http://fusesource.com
>>
>> Connect at CamelOne May 24-26
>> The Open Source Integration Conference
>> http://camelone.com/
>>
>
>
>
> --
> Claus Ibsen
> -----------------
> FuseSource
> Email: cibsen@fusesource.com
> Web: http://fusesource.com
> CamelOne 2011: http://fusesource.com/camelone2011/
> Twitter: davsclaus
> Blog: http://davsclaus.blogspot.com/
> Author of Camel in Action: http://www.manning.com/ibsen/
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
Connect at CamelOne May 24-26
The Open Source Integration Conference
http://camelone.com/
Re: [INFRA PROPOSAL] add "library upgrade" as issue type
Posted by Guillaume Nodet <gn...@gmail.com>.
It is globally available. Just try and let me know if you don't see it.
On Sat, Apr 23, 2011 at 09:18, Claus Ibsen <cl...@gmail.com> wrote:
> On Sat, Apr 23, 2011 at 8:35 AM, Guillaume Nodet <gn...@gmail.com> wrote:
>> Looks like I've just done that.
>> If you create a new issue, you should have a "Dependency upgrade" type now.
>>
>
> Hi Guillaume.
>
> How did you do that? It would be nice to have that for SMX and Camel
> as well, as we frequent upgrade libraries as well.
>
>
>> On Sat, Apr 23, 2011 at 08:28, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
>>> I have to check if I have permission to do that.
>>>
>>> I will let you know.
>>>
>>> Regards
>>> JB
>>>
>>> On 04/23/2011 08:26 AM, Andreas Pieber wrote:
>>>>
>>>> Can someone of us do this (I have no admin tab in JIRA :( ) or should
>>>> I create an issue at INFRA?
>>>>
>>>> Kind regards,
>>>> Andreas
>>>>
>>>> On Sat, Apr 23, 2011 at 8:23 AM, Guillaume Nodet<gn...@gmail.com> wrote:
>>>>>
>>>>> It sounds like a good idea.
>>>>>
>>>>> On Fri, Apr 22, 2011 at 23:25, Andreas Pieber<an...@gmail.com> wrote:
>>>>>>
>>>>>> Hey guys,
>>>>>>
>>>>>> On most projects I'm working on we have an own issue type "library
>>>>>> upgrade". The problem is that some ppl are interested into what libs
>>>>>> are upgraded between two releases and if those are scattered between
>>>>>> tasks and improvements in the changelog they are typically hard to
>>>>>> find. Adding an own issue type collects them quite nicely in the
>>>>>> changelog and in addition no one have to think if an upgrade is a task
>>>>>> or an improvement ;)
>>>>>>
>>>>>> WDYT? Kind regards,
>>>>>> Andreas
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Cheers,
>>>>> Guillaume Nodet
>>>>> ------------------------
>>>>> Blog: http://gnodet.blogspot.com/
>>>>> ------------------------
>>>>> Open Source SOA
>>>>> http://fusesource.com
>>>>>
>>>>> Connect at CamelOne May 24-26
>>>>> The Open Source Integration Conference
>>>>> http://camelone.com/
>>>>>
>>>
>>
>>
>>
>> --
>> Cheers,
>> Guillaume Nodet
>> ------------------------
>> Blog: http://gnodet.blogspot.com/
>> ------------------------
>> Open Source SOA
>> http://fusesource.com
>>
>> Connect at CamelOne May 24-26
>> The Open Source Integration Conference
>> http://camelone.com/
>>
>
>
>
> --
> Claus Ibsen
> -----------------
> FuseSource
> Email: cibsen@fusesource.com
> Web: http://fusesource.com
> CamelOne 2011: http://fusesource.com/camelone2011/
> Twitter: davsclaus
> Blog: http://davsclaus.blogspot.com/
> Author of Camel in Action: http://www.manning.com/ibsen/
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
Connect at CamelOne May 24-26
The Open Source Integration Conference
http://camelone.com/
Re: [INFRA PROPOSAL] add "library upgrade" as issue type
Posted by Claus Ibsen <cl...@gmail.com>.
On Sat, Apr 23, 2011 at 8:35 AM, Guillaume Nodet <gn...@gmail.com> wrote:
> Looks like I've just done that.
> If you create a new issue, you should have a "Dependency upgrade" type now.
>
Hi Guillaume.
How did you do that? It would be nice to have that for SMX and Camel
as well, as we frequent upgrade libraries as well.
> On Sat, Apr 23, 2011 at 08:28, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
>> I have to check if I have permission to do that.
>>
>> I will let you know.
>>
>> Regards
>> JB
>>
>> On 04/23/2011 08:26 AM, Andreas Pieber wrote:
>>>
>>> Can someone of us do this (I have no admin tab in JIRA :( ) or should
>>> I create an issue at INFRA?
>>>
>>> Kind regards,
>>> Andreas
>>>
>>> On Sat, Apr 23, 2011 at 8:23 AM, Guillaume Nodet<gn...@gmail.com> wrote:
>>>>
>>>> It sounds like a good idea.
>>>>
>>>> On Fri, Apr 22, 2011 at 23:25, Andreas Pieber<an...@gmail.com> wrote:
>>>>>
>>>>> Hey guys,
>>>>>
>>>>> On most projects I'm working on we have an own issue type "library
>>>>> upgrade". The problem is that some ppl are interested into what libs
>>>>> are upgraded between two releases and if those are scattered between
>>>>> tasks and improvements in the changelog they are typically hard to
>>>>> find. Adding an own issue type collects them quite nicely in the
>>>>> changelog and in addition no one have to think if an upgrade is a task
>>>>> or an improvement ;)
>>>>>
>>>>> WDYT? Kind regards,
>>>>> Andreas
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Cheers,
>>>> Guillaume Nodet
>>>> ------------------------
>>>> Blog: http://gnodet.blogspot.com/
>>>> ------------------------
>>>> Open Source SOA
>>>> http://fusesource.com
>>>>
>>>> Connect at CamelOne May 24-26
>>>> The Open Source Integration Conference
>>>> http://camelone.com/
>>>>
>>
>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
>
> Connect at CamelOne May 24-26
> The Open Source Integration Conference
> http://camelone.com/
>
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
CamelOne 2011: http://fusesource.com/camelone2011/
Twitter: davsclaus
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
Re: [INFRA PROPOSAL] add "library upgrade" as issue type
Posted by Guillaume Nodet <gn...@gmail.com>.
Looks like I've just done that.
If you create a new issue, you should have a "Dependency upgrade" type now.
On Sat, Apr 23, 2011 at 08:28, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
> I have to check if I have permission to do that.
>
> I will let you know.
>
> Regards
> JB
>
> On 04/23/2011 08:26 AM, Andreas Pieber wrote:
>>
>> Can someone of us do this (I have no admin tab in JIRA :( ) or should
>> I create an issue at INFRA?
>>
>> Kind regards,
>> Andreas
>>
>> On Sat, Apr 23, 2011 at 8:23 AM, Guillaume Nodet<gn...@gmail.com> wrote:
>>>
>>> It sounds like a good idea.
>>>
>>> On Fri, Apr 22, 2011 at 23:25, Andreas Pieber<an...@gmail.com> wrote:
>>>>
>>>> Hey guys,
>>>>
>>>> On most projects I'm working on we have an own issue type "library
>>>> upgrade". The problem is that some ppl are interested into what libs
>>>> are upgraded between two releases and if those are scattered between
>>>> tasks and improvements in the changelog they are typically hard to
>>>> find. Adding an own issue type collects them quite nicely in the
>>>> changelog and in addition no one have to think if an upgrade is a task
>>>> or an improvement ;)
>>>>
>>>> WDYT? Kind regards,
>>>> Andreas
>>>>
>>>
>>>
>>>
>>> --
>>> Cheers,
>>> Guillaume Nodet
>>> ------------------------
>>> Blog: http://gnodet.blogspot.com/
>>> ------------------------
>>> Open Source SOA
>>> http://fusesource.com
>>>
>>> Connect at CamelOne May 24-26
>>> The Open Source Integration Conference
>>> http://camelone.com/
>>>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
Connect at CamelOne May 24-26
The Open Source Integration Conference
http://camelone.com/
Re: [INFRA PROPOSAL] add "library upgrade" as issue type
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
I have to check if I have permission to do that.
I will let you know.
Regards
JB
On 04/23/2011 08:26 AM, Andreas Pieber wrote:
> Can someone of us do this (I have no admin tab in JIRA :( ) or should
> I create an issue at INFRA?
>
> Kind regards,
> Andreas
>
> On Sat, Apr 23, 2011 at 8:23 AM, Guillaume Nodet<gn...@gmail.com> wrote:
>> It sounds like a good idea.
>>
>> On Fri, Apr 22, 2011 at 23:25, Andreas Pieber<an...@gmail.com> wrote:
>>> Hey guys,
>>>
>>> On most projects I'm working on we have an own issue type "library
>>> upgrade". The problem is that some ppl are interested into what libs
>>> are upgraded between two releases and if those are scattered between
>>> tasks and improvements in the changelog they are typically hard to
>>> find. Adding an own issue type collects them quite nicely in the
>>> changelog and in addition no one have to think if an upgrade is a task
>>> or an improvement ;)
>>>
>>> WDYT? Kind regards,
>>> Andreas
>>>
>>
>>
>>
>> --
>> Cheers,
>> Guillaume Nodet
>> ------------------------
>> Blog: http://gnodet.blogspot.com/
>> ------------------------
>> Open Source SOA
>> http://fusesource.com
>>
>> Connect at CamelOne May 24-26
>> The Open Source Integration Conference
>> http://camelone.com/
>>
Re: [INFRA PROPOSAL] add "library upgrade" as issue type
Posted by Andreas Pieber <an...@gmail.com>.
Can someone of us do this (I have no admin tab in JIRA :( ) or should
I create an issue at INFRA?
Kind regards,
Andreas
On Sat, Apr 23, 2011 at 8:23 AM, Guillaume Nodet <gn...@gmail.com> wrote:
> It sounds like a good idea.
>
> On Fri, Apr 22, 2011 at 23:25, Andreas Pieber <an...@gmail.com> wrote:
>> Hey guys,
>>
>> On most projects I'm working on we have an own issue type "library
>> upgrade". The problem is that some ppl are interested into what libs
>> are upgraded between two releases and if those are scattered between
>> tasks and improvements in the changelog they are typically hard to
>> find. Adding an own issue type collects them quite nicely in the
>> changelog and in addition no one have to think if an upgrade is a task
>> or an improvement ;)
>>
>> WDYT? Kind regards,
>> Andreas
>>
>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
>
> Connect at CamelOne May 24-26
> The Open Source Integration Conference
> http://camelone.com/
>
Re: [INFRA PROPOSAL] add "library upgrade" as issue type
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
+1
Regards
JB
On 04/23/2011 08:23 AM, Guillaume Nodet wrote:
> It sounds like a good idea.
>
> On Fri, Apr 22, 2011 at 23:25, Andreas Pieber<an...@gmail.com> wrote:
>> Hey guys,
>>
>> On most projects I'm working on we have an own issue type "library
>> upgrade". The problem is that some ppl are interested into what libs
>> are upgraded between two releases and if those are scattered between
>> tasks and improvements in the changelog they are typically hard to
>> find. Adding an own issue type collects them quite nicely in the
>> changelog and in addition no one have to think if an upgrade is a task
>> or an improvement ;)
>>
>> WDYT? Kind regards,
>> Andreas
>>
>
>
>
Re: [INFRA PROPOSAL] add "library upgrade" as issue type
Posted by Guillaume Nodet <gn...@gmail.com>.
It sounds like a good idea.
On Fri, Apr 22, 2011 at 23:25, Andreas Pieber <an...@gmail.com> wrote:
> Hey guys,
>
> On most projects I'm working on we have an own issue type "library
> upgrade". The problem is that some ppl are interested into what libs
> are upgraded between two releases and if those are scattered between
> tasks and improvements in the changelog they are typically hard to
> find. Adding an own issue type collects them quite nicely in the
> changelog and in addition no one have to think if an upgrade is a task
> or an improvement ;)
>
> WDYT? Kind regards,
> Andreas
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
Connect at CamelOne May 24-26
The Open Source Integration Conference
http://camelone.com/