On Tue, Dec 9, 2008 at 11:12 AM, Upayavira <[EMAIL PROTECTED]> wrote:
> On Tue, 2008-12-09 at 19:56 +0100, Chris Chabot wrote: > > 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). > > Two tarballs is fine, but remember we vote on tarballs, not svn > revisions. But, if we're releasing both at the same time, we can vote on > both at the same time. > I'm +1 for two tarballs, since it is unlikely that most users of Shindig will want/need both code bases. However, I agree that we should vote on both at the same time. Any volunteers for the Java tarball + RAT? -Dan
