While I haven't looked at what Shiro has done, your explanation of the relevance of a buildable source package sounds fine.
----- Original Message ---- > From: ant elder <ant.el...@gmail.com> > To: general@incubator.apache.org > Sent: Wed, May 26, 2010 11:11:29 AM > Subject: Re: [VOTE] Release Shiro version 1.0.0-incubating > > On Wed, May 26, 2010 at 2:59 PM, Alan D. Cabrera < > ymailto="mailto:l...@toolazydogs.com"; > href="mailto:l...@toolazydogs.com";>l...@toolazydogs.com> > wrote: > > On May 26, 2010, at 2:00 AM, ant elder > wrote: > >> On Tue, May 25, 2010 at 11:32 PM, Kalle > Korhonen >> < > href="mailto:kalle.o.korho...@gmail.com";>kalle.o.korho...@gmail.com> > 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 >>> > href="http://maven.apache.org/developers/release/apache-release.html"; > target=_blank > >http://maven.apache.org/developers/release/apache-release.html. > 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: >>> > href="http://mail-archives.apache.org/mod_mbox/incubator-shiro-dev/201005.mbox/%3caanlktik_mke9dwlatmxnzq7kwcdbs3amsu5ulymkp...@mail.gmail.com%3e"; > > target=_blank > >http://mail-archives.apache.org/mod_mbox/incubator-shiro-dev/201005.mbox/%3caanlktik_mke9dwlatmxnzq7kwcdbs3amsu5ulymkp...@mail.gmail.com%3e >>> >>> > The issues solved for 1.0.0 (after the project entered Apache > incubator): >>> > href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310950&styleName=Html&version=12314078"; > > target=_blank > >https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310950&styleName=Html&version=12314078 >>> >>> > The tag to be voted upon: >>> > href="http://svn.apache.org/repos/asf/incubator/shiro/tags/shiro-root-1.0.0-incubating/"; > > target=_blank > >http://svn.apache.org/repos/asf/incubator/shiro/tags/shiro-root-1.0.0-incubating/ >>> >>> > Staging repo for binaries: >>> > href="https://repository.apache.org/content/repositories/orgapacheshiro-005/"; > target=_blank > >https://repository.apache.org/content/repositories/orgapacheshiro-005/ >>> >>> > Staging site: >>> > href="http://incubator.apache.org/shiro/static/1.0.0-incubating/"; > target=_blank > >http://incubator.apache.org/shiro/static/1.0.0-incubating/ >>> >>> > Project website (just for informational purposes, not to be voted > upon): >>> > target=_blank > >http://incubator.apache.org/shiro/ >>> >>> Guide to > testing staged releases: >>> > href="http://maven.apache.org/guides/development/guide-testing-releases.html"; > target=_blank > >http://maven.apache.org/guides/development/guide-testing-releases.html >>> >>> > 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". > > > href="https://repository.apache.org/content/repositories/orgapacheshiro-005/org/apache/shiro/shiro-all/1.0.0-incubating/"; > > target=_blank > >https://repository.apache.org/content/repositories/orgapacheshiro-005/org/apache/shiro/shiro-all/1.0.0-incubating/ > 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 > href="http://www.apache.org/dev/release.html#what-must-every-release-contain"; > target=_blank > >http://www.apache.org/dev/release.html#what-must-every-release-contain 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. > ...ant --------------------------------------------------------------------- To > unsubscribe, e-mail: > ymailto="mailto:general-unsubscr...@incubator.apache.org"; > href="mailto:general-unsubscr...@incubator.apache.org";>general-unsubscr...@incubator.apache.org For > additional commands, e-mail: > ymailto="mailto:general-h...@incubator.apache.org"; > href="mailto:general-h...@incubator.apache.org";>general-h...@incubator.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
