I think from a practicality point of view, having a tarball per code base makes sense, why download N mb when your not going to use it?
I'm thinking of whipping up a make_release.sh type script that'll create a release php-shindig tarball, it could copy in the sample container and features code into the php root and save us some of the possible confusion (it's happened a few times that people only copied the php dir, forgetting they also needed '../features' for instance). On Tue, Dec 9, 2008 at 7:02 PM, Kevin Brown <[EMAIL PROTECTED]> wrote: > What's expected in the tarball? Do we roll up the built jar(s) into the > tarball? Should there be separate tarballs for each code base? > > On Tue, Dec 9, 2008 at 5:28 AM, Chris Chabot <[EMAIL PROTECTED]> wrote: > > > I'll get a php-shindig tarball ready somewhere today (and post it's RAT > > results). > > > > However I'm not conferable enough with maven, wars, jars etc to take a > > swing > > at the java tarball, and I think Ian (who's been our release hero so far) > > is > > unavailable this week, so I'm hoping someone else can step up and take on > > that responsibility. > > > > On Tue, Dec 9, 2008 at 7:02 AM, Dan Peterson <[EMAIL PROTECTED]> > wrote: > > > > > Thanks for the note. > > > Who wants to run with getting the tarball ready and running RAT? > > > > > > -Dan > > > > > > On Mon, Dec 8, 2008 at 5:10 AM, 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 > > > > > > > > > > > > > > > > > >
