You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Grzegorz Kossakowski <gr...@tuffmail.com> on 2007/05/19 14:10:48 UTC
Separate projects on JIRA
Hello,
I would like to know your opinions on having multiple project on JIRA for Cocoon. I brought[1] this issue some time ago but then Reinhard
made an assumption that we would need our own JIRA instance.
Now I think this is not true. I've red somewhere that projects can have multiple JIRA projects, each one for releasable unit, but I cannot
recall source of this information. It's obvious that we are not going to have separate JIRA project for every releasable unit because they
are too many.
Therefore I propose to create new projects gradually as we see a strong need. I think that good indicator of the need for separate project
is that block/module starts to have more often releases so shared versioning space on JIRA is not enough any more.
This is my list of bocks/modules that should have separate project on JIRA:
- servlet-service-fw
- cocoon-forms
- cocoon-configuration
- maven plug-ins
Any comments? I could take care of dealing with JIRA guys during projects creation.
Do you know if moving issues between projects is possible on JIRA?
--
Grzegorz Kossakowski
http://reflectingonthevicissitudes.wordpress.com/
Re: Separate projects on JIRA
Posted by Grzegorz Kossakowski <gk...@apache.org>.
Grzegorz Kossakowski pisze:
> Hello,
>
> I would like to know your opinions on having multiple project on JIRA
> for Cocoon. I brought[1] this issue some time ago but then Reinhard made
> an assumption that we would need our own JIRA instance.
I forgot to put the link: http://article.gmane.org/gmane.text.xml.cocoon.devel/72265
--
Grzegorz Kossakowski
http://reflectingonthevicissitudes.wordpress.com/
Re: Separate projects on JIRA
Posted by Reinhard Poetz <re...@apache.org>.
Grzegorz Kossakowski wrote:
> Reinhard Poetz pisze:
>>
>> Could you make a more detailed proposal of what new projects you want
>> to be created and send it to this list first?
>>
>
> No problem. I guess that the list will include most of the artifacts you
> are currently releasing. Could provide current list of them? I'm little
> bit lost because it was proposed several times.
>
> BTW. What's the status of the release?
I'm finished with the creation of the artifacts and I'm currently testing them
in my applications. If everything works as expected, I will start the vote
tommorrow. There you will also find a list of all artifacts :-)
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
Re: Separate projects on JIRA
Posted by Grzegorz Kossakowski <gk...@apache.org>.
Reinhard Poetz pisze:
>
> Could you make a more detailed proposal of what new projects you want to
> be created and send it to this list first?
>
No problem. I guess that the list will include most of the artifacts you are currently releasing. Could provide current list of them? I'm
little bit lost because it was proposed several times.
BTW. What's the status of the release?
--
Grzegorz Kossakowski
http://reflectingonthevicissitudes.wordpress.com/
Re: Separate projects on JIRA
Posted by Reinhard Poetz <re...@apache.org>.
Grzegorz Kossakowski wrote:
> David Blevins pisze:
>>
>> On May 19, 2007, at 5:28 AM, Joerg Heinicke wrote:
>>
>>> On 19.05.2007 14:10, Grzegorz Kossakowski wrote:
>>>
>>>> I would like to know your opinions on having multiple project on
>>>> JIRA for Cocoon.
>>>
>>> If you have a look at [1] you'll see that Jira knows the concept of
>>> category. And like Avalon, Geronimo or whatever have multiple
>>> projects in their category it should be no problem to have the same
>>> for Cocoon.
>>
>> Not sure what kind of setup you guys have going on, but for stuff I
>> work with seems like for every "pool of version numbers" you more or
>> less have to have a Jira project. At least that's why Geronimo has
>> those projects -- each of those projects follows its own stream of
>> version numbers.
>
> I think we are going to have something similar. Blocks/modules that are
> released more frequently should have its own project on JIRA because
> it's impossible (or at least inconvenient)
I'd even say "unwanted"
> to keep all version ranges in
> sync.
>
> I see that no one objects the need for separate projects. Do I have to
> start a formal vote on it before asking INFRA folks for anything?
Could you make a more detailed proposal of what new projects you want to be
created and send it to this list first?
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
Re: Separate projects on JIRA
Posted by Grzegorz Kossakowski <gk...@apache.org>.
David Blevins pisze:
>
> On May 19, 2007, at 5:28 AM, Joerg Heinicke wrote:
>
>> On 19.05.2007 14:10, Grzegorz Kossakowski wrote:
>>
>>> I would like to know your opinions on having multiple project on JIRA
>>> for Cocoon.
>>
>> If you have a look at [1] you'll see that Jira knows the concept of
>> category. And like Avalon, Geronimo or whatever have multiple projects
>> in their category it should be no problem to have the same for Cocoon.
>
> Not sure what kind of setup you guys have going on, but for stuff I work
> with seems like for every "pool of version numbers" you more or less
> have to have a Jira project. At least that's why Geronimo has those
> projects -- each of those projects follows its own stream of version
> numbers.
I think we are going to have something similar. Blocks/modules that are released more frequently should have its own project on JIRA because
it's impossible (or at least inconvenient) to keep all version ranges in sync.
I see that no one objects the need for separate projects. Do I have to start a formal vote on it before asking INFRA folks for anything?
--
Grzegorz Kossakowski
http://reflectingonthevicissitudes.wordpress.com/
Re: Separate projects on JIRA
Posted by David Blevins <da...@visi.com>.
On May 19, 2007, at 5:28 AM, Joerg Heinicke wrote:
> On 19.05.2007 14:10, Grzegorz Kossakowski wrote:
>
>> I would like to know your opinions on having multiple project on
>> JIRA for Cocoon.
>
> If you have a look at [1] you'll see that Jira knows the concept of
> category. And like Avalon, Geronimo or whatever have multiple
> projects in their category it should be no problem to have the same
> for Cocoon.
Not sure what kind of setup you guys have going on, but for stuff I
work with seems like for every "pool of version numbers" you more or
less have to have a Jira project. At least that's why Geronimo has
those projects -- each of those projects follows its own stream of
version numbers.
-David
Re: Separate projects on JIRA
Posted by Joerg Heinicke <jo...@gmx.de>.
On 19.05.2007 14:10, Grzegorz Kossakowski wrote:
> I would like to know your opinions on having multiple project on JIRA
> for Cocoon.
If you have a look at [1] you'll see that Jira knows the concept of
category. And like Avalon, Geronimo or whatever have multiple projects
in their category it should be no problem to have the same for Cocoon.
Joerg
[1] https://issues.apache.org/jira/secure/BrowseProjects.jspa