Hi Carsten,

HttpComponents is also Maven2-based. Oleg has collected his actions
for a release in our Wiki, you may want to have a look at that (and
build a similar page for Felix?):
http://wiki.apache.org/jakarta-httpclient/HttpComponentsCoreReleaseProcess

It's way more than just calling Maven...

>> 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?

Well, you need a LICENCE and NOTICE file, and probably should
have at least a minimal README. Keeping them hidden in the JAR
will make the release different from all other distributables
at Apache, right?
Whether you want to release sources is of course a community
decision. But since it's Open Source Software, you probably
want to make the source for a particular release a little more
accessible than by posting a link to a Subversion tag? The people
that use the binary are supposed to look into the corresponding
source when they hit problems.

cheers,
  Roland

PS: I'm only subscribed to the list digest, don't know whether
the copy to the list will go through. Feel free to quote or
forward this mail if it doesn't.

Reply via email to