Hello, Thanks for your support! The 72 hours have passed and we have 10 positive votes, of which 3 are binding and 7 are non-binding. We now have the required number of positive binding votes and will therefore proceed with the release.
Thanks, Cory Johns Binding votes (3): +1 Rich Bowen +1 Daniel Gruno +1 Jim Jagielski Non-binding votes (7): +1 Dave Brondsema +1 Cory Johns +1 Daniel Hinojosa +1 Tim Van Steenburgh +1 Wayne Witzel III +1 Roberto Galoppini +1 Christopher Tsai Votes from the Incubator mailing list: http://mail-archives.apache.org/mod_mbox/incubator-general/201311.mbox/%3CCAGN0FaSkTrKpfVMwvC5LMcsPojU8DQ4K8%3DGhg7kJVHJRPxHFkA%40mail.gmail.com%3E Votes from the Allura mailing list: http://mail-archives.apache.org/mod_mbox/incubator-allura-dev/201310.mbox/%3CCAGN0FaRemYQmMLcd%3DEr91%2BL0zhwU1kyPQVeG4wMCeJ22_nALUg%40mail.gmail.com%3E On Sat, Nov 9, 2013 at 9:50 AM, Jim Jagielski <j...@jagunet.com> wrote: > Agreed. Not a blocker: Still +1 > > On Nov 8, 2013, at 1:52 PM, Dave Brondsema <d...@brondsema.net> wrote: > > > On 11/8/13 6:17 AM, Daniel Gruno wrote: > >> On 11/04/2013 07:09 PM, Cory Johns wrote: > >>> Hello, > >>> > >>> This is a call for a vote on Apache Allura 1.0.1 incubating. This is > our > >>> second attempt at an initial release, which specifically addresses the > >>> concerns raised in the previous, cancelled vote. > >>> > >>> A vote was held on developer mailing list and it passed with 8 +1's, > and 0 > >>> -1's or +0's (with one of the +1's being from a project mentor) and now > >>> requires a vote on general@incubator.apache.org. > >>> > >>> The [VOTE] and [DISCUSS] threads can be found at: > >>> [VOTE]: > >>> > http://mail-archives.apache.org/mod_mbox/incubator-allura-dev/201310.mbox/%3CCAGN0FaRemYQmMLcd%3DEr91%2BL0zhwU1kyPQVeG4wMCeJ22_nALUg%40mail.gmail.com%3E > >>> [DISCUSS]: > >>> > http://mail-archives.apache.org/mod_mbox/incubator-allura-dev/201310.mbox/%3CCAGN0FaR0FeNuMB2%3D_%2Bea8Z15a94T-OR9oamk4v7LhxF-ijxf3Q%40mail.gmail.com%3E > >>> > >>> Source tarball and signature are available at: > >>> > >>> > https://dist.apache.org/repos/dist/dev/incubator/allura/allura-incubating-1.0.1.tar.gz > >>> > >>> > https://dist.apache.org/repos/dist/dev/incubator/allura/allura-incubating-1.0.1.tar.gz.asc > >>> > >>> Checksums: > >>> MD5: 06bd5311ab4fc5103e4fb96e737da2ff > allura-incubating-1.0.1.tar.gz > >>> SHA1: 76a6bfdaee1a3c38e920f3f173fd920e1f8aefd0 > >>> allura-incubating-1.0.1.tar.gz > >>> SHA512: > >>> > 813a15b1c32a90e6404bd432874b7ed3ede3b62162d39fde35f6bbfd540f0f75cfc9ca348eeaac3992b2455366339133d0d69524fe118059edb20a440ed7f09c > >>> allura-incubating-1.0.1.tar.gz > >>> > >>> Note: The checksum values are correct, but the format of the checksum > files > >>> is off slightly (single instead of double space after checksum, > absolute > >>> path for file name) preventing automatic verification with the -c > option > >>> without minor editing of the files. (This was discussed on the > [DISCUSS] > >>> thread [1] and the current files are what were voted on.) > >>> > >>> The KEYS file can be found at: > >>> http://www.apache.org/dist/incubator/allura/KEYS > >>> > >>> The release has been signed with key (449C78B1): > >>> > http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0xDB6E071B449C78B1 > >>> > >>> Source corresponding to this release can be found at: > >>> Commit: 924e0204706aeb5367e60df19ba38b26ac4474a3 > >>> Tag: asf_release_1.0.1 > >>> Browse: > >>> > https://git-wip-us.apache.org/repos/asf?p=incubator-allura.git;a=shortlog;h=refs/tags/asf_release_1.0.1 > >>> > >>> The RAT report is available at: > >>> https://sourceforge.net/p/allura/pastebin/525eea8f485acd3ba7c37a22 > >>> > >>> Vote will be open for at least 72 hours (2013-11-07 12PM IST). > >>> > >>> > >>> [1]: > >>> > http://mail-archives.apache.org/mod_mbox/incubator-allura-dev/201310.mbox/%3CCAGN0FaRy5GNSEv7_km_h8LmO3ZPWSsyOzXUqRh5tuVhFhNpSzQ%40mail.gmail.com%3E > >>> > >> +0.9 (I might be inclined to add another 0.1 if you can sway me) > >> > >> There is still a reference to sourceforge inside the allura base - when > >> I create a new project and click on the Git tab, I get this: "Did you > >> get asked for your SourceForge password during this process? You can > >> securely use your Git repository and avoid having to re-enter your > >> password by setting up an ssh-key." > >> > > > > I don't think this is a critical or legal blocker, so given the > > social/procedural overhead of getting an Allura release out, I think > we'd be > > better off to ship this release as-is. We can fix this for our next > release. > > > > There are some other less-prominent references to SourceForge in the > codebase as > > well. > > > > > > -- > > Dave Brondsema : d...@brondsema.net > > http://www.brondsema.net : personal > > http://www.splike.com : programming > > <>< > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
