I'm kicking this over to a new thread, so people have a clear opportunity to jump in if they have comments. +1 to getting the voting started by the end of the week
Thanks for keeping the ball rolling, -Dan ---------- Forwarded message ---------- From: Chris Chabot <[EMAIL PROTECTED]> Date: Thu, Dec 11, 2008 at 6:55 AM Subject: Re: How to do this release To: [email protected] Hey Guys, I'm trying to get our tarballs rolled up and ready for inspection and voting on shindig-dev by the end of today. Ian has been a hero and stepped up to create the java based tarballs for us, which you can already find at: http://people.apache.org/~ieb/shindig_tars/ the 2 tarballs that are relevant there (or pick the zip/bz2 depending on preference): shindig-1.0.0-incubating-SNAPSHOT-binary.tar.gz < http://people.apache.org/%7Eieb/shindig_tars/shindig-1.0.0-incubating-SNAPSHOT-binary.tar.gz > shindig-1.0.0-incubating-SNAPSHOT-source.tar.gz < http://people.apache.org/%7Eieb/shindig_tars/shindig-1.0.0-incubating-SNAPSHOT-source.tar.gz > (on the final submission for voting on shindig-dev and [EMAIL PROTECTED], we'll rename them s/-SNAPSHOT//) The PHP version of shindig i'm still creating a build release script for, some last minute bug fixes got in the way of making progress in that area, but I'm feeling quite confident that will be done before the end of the day, so I'll have a php release tarball ready for voting by then too. I've run the RAT tool (linked below in Upayavira's post) against shindig, and while there is a bit of noise, everything that i have been able to identify in it's output is either xml files without license headers (which is good, could break stuff), the non recognized BSD license files in the phpunit and zend libraries that php-shindig uses, and such cases; But no missing Apache license files where they should've been as far as I could judge.But please feel free to test for your self (on the svn checkout of the 1.0.x branch) and sift through the results, it's always possible that i missed something. Since we're approaching the time where people tend to go on holiday (second half of dec), I'm hoping to have our tarbals submitted for inspection & discussion on the [EMAIL PROTECTED] list by end of day friday, so that we have all next week to deal with the feedback & the voting process there. To be able to do so, we do need to speed through our shindig-dev voting process, so I'm hoping that if you have any feedback on the release so far (the 1.0.x branch is publicly available & has been for a while, and the java tarbals are available for inspection already too), please share now; If you feel there are any reasons to block this release, please do feel to speak up, I'm completely sure everyone involved with shindig would much rather see us do a good and proper release then to rush something, so please do speak up if you have any concerns! This is a very exciting time for all of us, the first time we're doing an actual release and that will be an important milestone for us, and signify another step in the maturing of the project. I look forward to your feedback & lets make this a great release! -- Chris On Mon, Dec 8, 2008 at 2:10 PM, Upayavira <[EMAIL PROTECTED]> wrote: > Just so that everyone is on the same page, I thought I'd mention that > there's a bit of process required for the coming release. > > Because it is our first release, but more importantly because it is > still an incubator release. As such, it is the Incubator PMC that will > actually be releasing the code, so they need to vote to approve it. > > Also, the RAT (release audit tool) (http://incubator.apache.org/rat) is > a very helpful tool for checking that all the legal details are correct > - licenses are in place and so on. We will need to use it on this > proposed release. > > Here's how I see the process going: > > * Put a tarball up online somewhere (e.g. in someone's home directory > on people.apache.org) > * Someone run RAT against the tarball, and see what sort of results > it gives > * Deal with any issues identified by RAT > * Vote ourselves that we want to release that tarball > * Announce the tarball on [EMAIL PROTECTED] > * deal with any responses we get > * Put a vote to [EMAIL PROTECTED] to release that tarball > * Once that vote is complete, we can release it, by uploading it to the > incubator release area, which will feed it into the Apache mirror > system. > > Upayavira > > >
