Rafal Krzewski <[EMAIL PROTECTED]> writes:
> Jon Stevens wrote:
> > > What do you think of tagging "stable points" in the Turbine CVS tree using
> > > a convention like Turbine-M1, Turbine-M2, etc... for the benefit of the
> > > Turbine-dependent projects ?
> >
> > -1 That is the same as doing a release and we are not ready for release yet.
>
> It's not the same, but it's would be quite hard to implement. How can
> you
> determine if today's snapshot is stable or not? We don't have unit tests
> yet. The only thing is tagging after introducing and roughly testing
> major new features (so it would be depend on feature set scheme).
>
> If we were to do that, we need strict policy for tagging, otherwise
> it will soon turn into unusable mess. You can't delete a tag once it
> is set, you know.
>
> Right now +0 from me.
I'm +1 on periodic tags, stable or not. The fact that Jetspeed uses
Turbine gives Turbine more developers. I agree that a full release is
a good thing and would like to see it happen when possible, but
periodically tagging the CVS source code is not a bad thing if done
uniformly with reasonably long wait times in between tags. I suggest
tagging in conjunction with TDK releases for the time being.
Daniel Rall
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
