Related strictly to commons I would suggest that the one in charge with releasing should be somebody that can allocate time to this process as I presume that commons will be released very often due to the nature of this subproject. If we are looking back as Karl was bussy there was quite a gap between posting of a new wrapped jar and the time it got released. Regards, Alin Dreghiciu
On 7/24/07, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
Marcel Offermans wrote: > First of all, don't take this the wrong way, but I thought that only our > release manager could call a vote for releasing artifacts? This is up to us to define this. There is no official position of a release manager in an apache project. But it's common sense to apoint someone to do this stuff. Depending on the work/project there is only one release manager or several. It makes sense to define who is responsible for releasing what in order to avoid confusion. But that's up to the project to define this. Having one release manager adds all the work to one single person (which can get very annoying over time) and also can lead to problems over time. What if a release is required and the release manager is not available? etc. But everyone can start a vote on something :) I personally think that it makes sense to split up the work for the release as Felix is a hugh project with many artifacts. And my idea was to help out in uncritical areas like commons. It has nearly no dependencies to the rest of Felix. > I happen to > know he's on holiday for the next two weeks. Furthermore, we still are > in the middle of releasing the framework itself, so I would suggest we > include these artifacts in the next build. Richard already mentioned > wanting to do an 1.0.1 soonish, so together with these artifacts that > would make a good second release. Hmm, yes this is one possibility - but as there are many modules in commons I personally would do a separate release of these. It's independent and doing a 1.0.1 release of the framework has no effect on commons. So, its up to us if we want to load all the work onto Karl (who did a great job btw). In general, if someone is willing to scratch an itch, I wouldn't stop him or her - but that's my personal opinion. And I'm fine with whatever we all think is best. Carsten -- Carsten Ziegeler [EMAIL PROTECTED]
