Hi Dan, thanks for the tons of work!
Unfortunately this cannot be an "official Apache" release, please mind that. When there is an release, 3 PMC members must vote +1. In incubating case 3 IPMC members must also vote +1. And with the current state of Ripple, this is not really likely it happens. We first need to clean up IP things and such. Then IPMC members usually find a LOT of problems with the first release. If you have released something, it also should not be named Ripple as it confuses people. It also cannot live on ASF hardware until the IPMC has approved this. Of course it is ok if you would flesh out an own package, rename it, and give it out to people. It just is not ok to have it in the name of ASF. Could you tell what it exactly means when you say "published"? Is it just a tag in source code? In ASF terms, a tag is not a release and so I think its ok. Providing it on a.org/dist is of course bad I would say, lets deal with release requirements soon and start fixing issues which prevents them. Cheers Christian On Thu, May 30, 2013 at 4:56 PM, Dan Silivestru <[email protected]> wrote: > Hi All, > > We just published Ripple 0.9.17 with a few bug fixes that would have caused > Ripple to not initialize. > > The rest of this email is for the BlackBerry folks. Since you own both the > BlackBerry and the chrome store releases you might want to consider doing a > release to those locations. > > Thanks, > > -- > Dan Silivestru > +1 (519) 589-3624 -- http://www.grobmeier.de https://www.timeandbill.de
