Carsten Ziegeler wrote:
> Joerg Heinicke wrote:
>
<snip />
>>Now the confusion starts. IMO we should have clear
>>version/repository matchings.
>>
>
> Yes, a clear matching is required. We would have the clear matching
> of "Any cocoon version >= 2.1 is in the cocoon-2.1 repository" :)
>
LOL.
>
>>>Of course, if we follow this road, our repositories would
>>
>>have wrong
>>
>>>names, but this imho doesn't really matter and we could rename the
>>>cocoon-2.2 repository without any problems.
>>
>>I don't agree. This naming issue really matters. It's IMO
>>much more important than non-upgrades during project's
>>lifetime. If we follow the proposal the above cries for a
>>cocoon-2 repository (the current 2.1) to make this at least clear.
>>And each branch is moved into a new repository.
>
> Now, actually, I didn't want to get into the "repository vs. branches
> and naming" discussions :) Ok, but we don't need to make a repository
> just because we change the version number. It only makes sense
agree
> if we continue the development. We end up in to many repositories
> that are actually unused.
> I don't see any problem with branching a previous version if
> the need arises.
>
agree, we should learn the lesson of the repository names we gave, not
let them prevent us from doing a proper release management
-marc=
--
Marc Portier http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog at http://blogs.cocoondev.org/mpo/
mpo@outerthought.org mpo@apache.org
|