Three days minimum. This is your chance to try out 1.0.0 before it becomes official - if there are any bugs found after the release is done, it'll take considerably longer to get them fixed and pushed to a new release.
Kalle On Thu, May 20, 2010 at 8:00 PM, Tauren Mills <[email protected]> wrote: > Kalle, > > Thanks for the info. I'm glad to see progress is being made toward a > release. Are we talking about a day or two before Shiro is officially > available from a non-snapshot maven repository become? Or does the > voting process take a while? > > If it will only be a day or two, I'll just wait. If not, I'll grab the > release and will manually remove the jars from my repo if updates > happen. > > Tauren > > > On Thu, May 20, 2010 at 7:49 PM, Kalle Korhonen > <[email protected]> wrote: >> On Thu, May 20, 2010 at 7:20 PM, Tauren Mills <[email protected]> wrote: >>> The latest snapshot available in the repository I'm using is 172, and >>> doesn't work if I make this change to my spring config (I get an >>> IllegalArgumentException): >>> https://repository.apache.org/content/repositories/snapshots/org/apache/shiro/shiro-core/1.0-incubating-SNAPSHOT/ >> >> That's because 1.0.0 was moved to a branch and it's not covered by CI >> build. I can't do anything about it, last I checked only PMC members >> were allowed permissions to the Hudson instance. >> >>> I've been waiting for a new snapshot to appear, but it hasn't yet and >>> it's been several hours. Is this because snapshots are now going to >>> here instead? >>> https://repository.apache.org/content/repositories/orgapacheshiro-004/ >> >> No snapshot there, but this our staged 1.0.0 release - basically it >> means these are the binaries for proposed 1.0.0 release. Official >> email on that is yet to be sent out, but by all means you could try >> them out - the only caveat is that if we redo the 1.0.0 release you >> need to manually delete the 1.0.0 Shiro libs from your local Maven >> repository. The next step is that a limited number of people try out >> the source in 1.0.0 tag (or the binaries from the staging repo for >> convenience), we vote on the release and if succesful, release 1.0.0 >> and deploy it to the public repositories. >> >> Kalle >> >
