I agree that it is a bit nicer to wait until they appear (fewer 'how come my build doesn't 'just work'! experiences). Unless anyone objects, I'll post the announcement once I verify the binaries are in Maven central.
Cheers, Les On Mon, Jan 23, 2012 at 11:52 AM, Kalle Korhonen <[email protected]> wrote: > On Mon, Jan 23, 2012 at 11:18 AM, Les Hazlewood <[email protected]> wrote: >> I _just_ released the staging repo a minute or two ago but havent made >> any announcements. >> With the previous two releases (incubating and 1.1.0), we made the >> announcement and noted to wait for 24 to 48 hours to wait for >> propagation to maven central. >> Is this something that (ideally) should not be done? > > Lots of projects do it that way, but announcing only after the bits > have hit central is much more user friendly, to me at least. > Completely up to us though, there are no hard rules either way. > > Kalle > > >> On Mon, Jan 23, 2012 at 10:16 AM, Kalle Korhonen >> <[email protected]> wrote: >>> Les, have you released from the staging repo (the staging repo is >>> still available)? I would hold off any announcements until the >>> binaries are in Maven central (yes, I know we are technically >>> releasing just the source, but...). >>> >>> Kalle >>> >>> >>> On Sun, Jan 22, 2012 at 11:34 PM, Les Hazlewood <[email protected]> >>> wrote: >>>> This vote is now closed. The vote passes with three binding +1s and >>>> no -1 or 0 votes. >>>> >>>> I'll make the announcement and update the website as soon as possible >>>> - probably tomorrow (Monday, January 23rd). >>>> >>>> Thanks, >>>> >>>> Les >>>> >>>> On Fri, Jan 20, 2012 at 3:50 PM, Jeremy Haile <[email protected]> wrote: >>>>> +1 binding >>>>> >>>>> On Jan 20, 2012, at 4:17 PM, Kalle Korhonen <[email protected]> >>>>> wrote: >>>>> >>>>>> Note that only pmc votes are binding: >>>>>> shiro-pmc >>>>>> SVN id Name >>>>>> clr Craig L Russell >>>>>> jhaile Jeremy Haile >>>>>> kaosko Kalle Korhonen >>>>>> lhazlewood Les Hazlewood >>>>>> pledbrook Peter Ledbrook >>>>>> >>>>>> Kalle >>>>>> >>>>>> >>>>>> On Fri, Jan 20, 2012 at 12:33 PM, Allan Ditzel <[email protected]> >>>>>> wrote: >>>>>>> +1 (binding) >>>>>>> >>>>>>> On Jan 19, 2012, at 9:53 PM, Les Hazlewood wrote: >>>>>>> >>>>>>>> This is a call to vote in favor of releasing Apache Shiro version >>>>>>>> 1.2.0. >>>>>>>> >>>>>>>> The 59 issues solved for 1.2.0 (since the 1.1.0 release): >>>>>>>> >>>>>>>> https://issues.apache.org/jira/secure/IssueNavigator!executeAdvanced.jspa?jqlQuery=project+%3D+SHIRO+AND+fixVersion+%3D+%221.2.0%22+AND+%28status+%21%3D+Open+and+status+%21%3D+%22In+Progress%22%29+ORDER+BY+priority+DESC&runQuery=true&clear=true >>>>>>>> >>>>>>>> Changes from the first two release attempts: >>>>>>>> - openId4j module completely removed from source >>>>>>>> - Subversion release tag is now named 'shiro-root-1.2.0' for >>>>>>>> consistency with previous release tags >>>>>>>> >>>>>>>> The tag to be voted upon: >>>>>>>> https://svn.apache.org/repos/asf/shiro/tags/shiro-root-1.2.0 >>>>>>>> >>>>>>>> Staging repo for binaries: >>>>>>>> https://repository.apache.org/content/repositories/orgapacheshiro-107 >>>>>>>> >>>>>>>> Project website (just for informational purposes, not to be voted >>>>>>>> upon): >>>>>>>> http://shiro.apache.org/ >>>>>>>> and maven static generated site (for informational purposes, not to be >>>>>>>> voted upon): >>>>>>>> people.apache.org:/www/shiro.apache.org/static/1.2.0 or >>>>>>>> http://shiro.apache.org/static/1.2.0 once it propagates to web servers >>>>>>>> >>>>>>>> Guide to testing staged releases: >>>>>>>> http://maven.apache.org/guides/development/guide-testing-releases.html >>>>>>>> >>>>>>>> Vote open for 72 hours. Please do examine the source and binaries >>>>>>>> before voting. >>>>>>>> >>>>>>>> [ ] +1 >>>>>>>> [ ] +0 >>>>>>>> [ ] -1 (please include reasoning) >>>>>>>
