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é <[email protected]> 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<[email protected]> wrote: >>> >>> It sounds like a good idea. >>> >>> On Fri, Apr 22, 2011 at 23:25, Andreas Pieber<[email protected]> 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/
