Jörn Nettingsmeier wrote:
Richard Frovarp wrote:
Anyone against changing our Cocoon version in trunk to a stable
version of Cocoon? It would probably be good to start testing against
the version we will be releasing against.
i'd rather we freeze our cocoon external at the current revision. is
that possible? downgrading to the last release would be quite a step
back, and possibly invalidate much of the testing and measurements
that have already been done.
i agree we should protect our users from regressions in the 2.1 dev
tree, but going back a year or so seems an odd thing to do in open
source land...
It might be, but does anyone here keep enough track of Cocoon to be able
to do this? We really should be against a stable revision. Otherwise, if
we just freeze we'll have to keep track of relevant patches to the
subsequent revisions and back port the patches to our revision. That
doesn't sound like fun.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
