> Even the old method of just releasing something every few months with > version number++ worked out reasonably good. > > There was never a perfect version, but new features got out there, bugs > would be found, etc. > > I might be more inclined to call it version 1.50 - the trunk has moved > quite a bit from 1.12, but is still compatible with it (the way some things > work is different). I'm not sure what the goal for 2.0 is - needs to be > something realistic, but I could also see that where we are may be half way > there. > > then every few months, make a new release - 1.51, 1.52, or maybe skip > going to 1.60, 1.70, etc. if significant changes.
Fine by me, as long as someone actually manages the releases :) Nicolas -- http://nicolas.weeger.org [Mon p'tit coin du web]
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ crossfire mailing list [email protected] http://mailman.metalforge.org/mailman/listinfo/crossfire
