[crossfire] Release?

[Nicolas Weeger]

Hello.

>   Yes, that is the ideal case, especially if there is lots of active
> development.
>
>   If there isn't, it is simpler to just freeze the trunk gate for anything
> but bug fixes needed for the 1.50 release.  That way quality can get
> better, without the overhead of a branch, potentially needing to do merges
> (a fix in trunk needing to get in for the 1.50 release or vice versa), etc.
>
>   The other thing is we don't typically make patches a release, so the
> branch isn't that useful in that area - instead, we just say it will be
> fixed in the next release.  If we do releases on a regular basis, that
> isn't that bad.


Well, I can see quite many things in the pipe lately - healthbars being one, 
and other fun things coming.

So totally freezing trunkmay not be a great idea, or it should be really a 
short time period :)


If we are still thinking of end of march, what should be done right now?

AFAIK the Windows build works (more or less), so I could produce a version if 
needed.



Nicolas
-- 
http://nicolas.weeger.org [Mon p'tit coin du web]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : http://mailman.metalforge.org/pipermail/crossfire/attachments/20100320/a3caee82/attachment.pgp