[crossfire] 1.60 release thoughts

[Nicolas Weeger]

Hello.

> - Within the file release on sourceforge, I think it makes more sense to
> just have the version directories at the top (eg, 1.60.0, 1.50.0), and
> then under each one, put all the associated files - server, maps, client,
> different clines (linux, windows, java, etc).

Agreed, makes sense.




> - At some point, the legacy character creation code should get removed, and
> related, basically all the ST_ values/player_set_state().

Makes sense too. Many commands (join party, form party) should be first handled 
by client to get player's input.
Note that there'd be some return value for commands, eg "join party <name>" 
with a return value of "-1 wrong password" so the client can display the 
password prompy.




> - For ChangeLog/CHANGES file:  I suggest the ChangeLog file get generated
> by svn2cl - this is already done for maps.  But each area also has a
> CHANGES file, which updated by hand but is used to note
> improvements/things of more general interest - hard to say where to really
> draw the line, but reformatting, minor bug fixes would not go in the
> CHANGES file - big features would.  Maybe the determination is anything
> that actually affects gameplay?  Thus, bug fixes wouldn't typically get
> put in (they may change gameplay because someone is exploiting a bug). 
> One reason I bring this up is that with the maps ChangeLog file from SVN,
> really no way to get any real useful content from that - I pretty much
> used the crossfire traffic - it is that type of stuff that could perhaps
> get put in the CHANGES file.


I think the manually made file should only list significant (and maybe only 
player-related?) changes, not all the minutia we have now.
So crossfire-traffic would just be a copy of that file.



Nicolas
-- 
Mon p'tit coin du web - http://nicolas.weeger.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: This is a digitally signed message part.
URL: <http://mailman.metalforge.org/pipermail/crossfire/attachments/20110206/3f572d8c/attachment.pgp>