Rafal Krzewski wrote:
>
> 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).
>
My point exactly, if you don't know if the CVS is stable, how do *I* (or any
external party) know that the snapshot is stable ? I just don't like the
"try and hope" approach we use currently because it may happen that we upgrade
out Turbine.jar just when a feature we need is being worked on.
> 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 understand that it's not easy to implement properly but I could not think of
anything better. A release would be ideal, of course :)
--
Rapha�l Luta - [EMAIL PROTECTED]
Vivendi Universal Networks - Services Manager / Paris
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
