incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ant elder <>
Subject Re: [VOTE] Release Shiro version 1.0.0-incubating
Date Wed, 26 May 2010 15:11:29 GMT
On Wed, May 26, 2010 at 2:59 PM, Alan D. Cabrera <> wrote:
> On May 26, 2010, at 2:00 AM, ant elder wrote:
>> On Tue, May 25, 2010 at 11:32 PM, Kalle Korhonen
>> <> wrote:
>>> This is the first incubator release for Apache Shiro, version
>>> 1.0.0-incubating. The release is made following the standard
>>> Apache/Maven release process as documented at
>>> This
>>> is a lazy consensus vote as we already received 3 binding IPMC +1
>>> votes for the PPMC release vote on shiro-dev.
>>> PPMC release vote thread:
>>> The issues solved for 1.0.0 (after the project entered Apache incubator):
>>> The tag to be voted upon:
>>> Staging repo for binaries:
>>> Staging site:
>>> Project website (just for informational purposes, not to be voted upon):
>>> Guide to testing staged releases:
>>> Lazy consensus, vote open for 72 hours.
>>> [ ] +1
>>> [ ] +0
>>> [ ] -1
>> I can't find all the source for the release. AFAICT the only way to
>> recreate all the release artifacts would be from the svn tag but thats
>> not enough as an ASF release must include a source release. If I've
>> just missed it and all the source is there somewhere then could you
>> provide the link?
> All the artifacts have sources and javadocs in the same "directories".

AIUI all ASF releases MUST have _buildable_ source. The source jars
included in those directories are not buildable. The idea behind this
is that the ASF deals with source code and releases are of source
packages that enable anyone to go tinker with that source, but you
can't do so much useful tinkering if you can't build the source. See
and various emails that fly around on other mailing lists.

I believe the latest Maven release plugin and Apache parent pom.xml
will create the correct packages now. You probably could reconstruct a
buildable source from whats in the Maven repo and if this was a small
release like a single Maven plugin or something it could have been
argued that this was ok and could just be updated to the new Maven
release for next release, but this is something like 20 modules so to
recreate it would be quite a job - working out and recreating the
correct directory structure, unzip all the source jars into the
correct place, download all the pom.xml's and rename them and put them
in the right place etc.

Or anyone leap in here and explain i've misunderstood the policy.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message