On 7/26/07, Carsten Ziegeler <[EMAIL PROTECTED]> wrote: > Niclas Hedhman wrote: > > On Tuesday 24 July 2007 20:53, Carsten Ziegeler wrote: > >> Now, I have the hope that releasing is just a matter of invoking maven > >> (with the correct arguments). > > > > First step is just the production of a parent pom, for the Commons to depend > > on. IMHO, that is not really a release (no tarball) and can be done by lazy > > consensus (go ahead). > Yes, I agree - good idea. > > > > > Second step to release Commons would be a proper release with tarball /dist > > stuff, and requires Vote of the PMC for legal reasons. > Yes, this raises the question of how the release of commons should look > like. So far I thought about just releasing the pom and the jar - not > sure if we need a src and bin dist here?
I'm not sure I really like the idea that we create all those artifacts of other projects. I was assuming that we would only provide the wrapper pom's as a starting point for the projects to ultimately make their stuff available as bundles by themselves. It might just be me so fell free to ignore this if nobody else has a strange felling about providing and maintaining all those artifacts... regards, Karl > > IMHO, Carsten is more than qualified to handle these things, as he has > > released Cocoon several times in the past, which is one hell of a beast... > > So, don't hinder the guy ;o) > Thanks - now you put even more pressure on me :) > > Carsten > > > -- > Carsten Ziegeler > [EMAIL PROTECTED] > -- Karl Pauls [EMAIL PROTECTED]
