Greetings all, The coho tool has been updated and I'm hoping we're ASF release compliant now. This is now what coho produces: http://people.apache.org/~goya/
There are a few last issues, specifically not having all the license and notice information in there. I think there are a few platforms that don't have some of these files so when those get updated, I can just copy and paste that info into the master license/notice file. Otherwise, I *think* we're good. Please let me know if there are any issues. On 24 February 2012 22:14, Jukka Zitting <[email protected]> wrote: > Hi, > > Sorry for the delay. The KEYS file just needs to be available in the dist > directory where you place the official release artifacts. See the > www.apache.org/dev docs on release signing and distribution. > > It would be helpful if you could cut rc release packages for review based > on the rc1 tags. It's easier to look at the actual bits than trying to > deduce things from the script. > > BR, > > Jukka Zitting > > On Friday, February 24, 2012, Steven Gill wrote: > > > > bump. Need to know if we are being compliant to ASF release policies if > we > > want to make 1.5 the first official apache release! > > > > On Wed, Feb 22, 2012 at 9:50 AM, Steven Gill <[email protected]> > wrote: > > > > > Hey Everyone, > > > > > > So coho (https://github.com/stevengill/coho) now does gpg signing. I > > > think that the releases being made by coho are apache release compliant > but > > > I would love some input from the mentors. > > > > > > Right now, we have a KEYS file that has public keys. Where does this > get > > > uploaded? > > > > > > If all things look good, we could potentially make 1.5 our first > official > > > apache release. Please advise! > > > > > > Thanks, > > > -Steve > > > > > > -- > BR, > > Jukka Zitting > -- Timothy Kim
