Paul Lindner from hi5 wrote to a similar question from Eiji (from Goo):
At hi5 we're using Piston (http://piston.rubyforge.org/) +
subversion 1.5 to maintain a vendor branch and pull changes into our
local repo as needed. This makes keeping up with the rapid code
changes much easier.
See: http://www.hi5networks.com/platform/ for our Trac instance
running on top of this.
On Aug 5, 2008, at 7:37 PM, Dan Peterson wrote:
For the people that are running live Shindig instances, can you
chime in
with what revision number you're using? Or how you manage keeping up
to
date? It seems like there are likely some best practices there.
I'm definitely looking forward to a stable incubator release as we
wrap up
this next version of the spec.
-Dan
On Tue, Aug 5, 2008 at 4:20 AM, Chris Chabot <[EMAIL PROTECTED]>
wrote:
Our current goal is to do a 'release' when we finished 0.8 support.
I call it an release between quotes, since apache is quite explicit
that an
release from incubation isn't an 'official apache branded release',
however
they don't oppose incubation releases either as long as we are very
explicit
about that :)
That all being said, quite a few partners choose not to sync every
day, but
pick a stable snapshot and build on top of that .. when that
snapshot is,
that's completely on the developers doing the snap-shotting :)
-- Chris
On Aug 5, 2008, at 1:09 PM, Chunlei Niu (牛春雷) wrote:
Hi,
Is there any stable version or milestone of Shindig? Then the
codes don't
need syncing everyday.
Thanks.
Chunlei
