[CF-Devel] Re: [Crossfire-cvs] CVS: crossfire/lib artifacts,1.26,1.27

[Mark Wedel]

gros wrote:
>
     
      - I thought that Crossfire-0.98.0 was the last step before 1.0 release and
     
     >
     
      that the only additions that would be integrated were bugfixes. Strangely,
     
     >
     
      the Ring of Benevolence doesn't seem to be a bugfix at all... Does it mean
     
     >
     
      that the Crossfire development team changed their projects and finally
     
     >
     
      decided to accept new additions, or is it just the manifestation that only
     
     >
     
      some people are allowed to make such additions ? If so, please send an
     
     >
     
      official 'Authorized Developers List' so other coders will not loose time on
     
     >
     
      Crossfire.
     
     
 This is probably my fault.  

 There is certainly a 'code' freeze.  However, I didn't worry about most of the
map, image and arch changes (and in fact, did not really pay attention to them
very much) - changes to those would not affect reliability of the server, which
was my chief concern.

 And in that sense, this is still true - the server is unlikely to be any less
reliable with these new artifact changes.  However, as suggested, there are
balance changes.   Even that probably isn't a big deal, but then again, the
changes to arch should probably not be wide open.

 Actually, my bigger worry is frequency of the objects - the treasurelists and
artifact generation lists are have a little voodoo involved for generation of
objects, and often it takes a little while to get the tweeking just right.

 I was seriously considering revoking all CVS access to prevent unauthorized
changes, but even with that, I really only wanted to restrict the server area
(which is not really possible with sourceforge), and it never seemed like that
big a deal.  And to be honest, it still isn't that big a deal.  Other option
would have been to do a branch for 1.0 stability (as I will still need to do one
for post 1.0 patches/releases)

 Actually, I'm very happy people are looking over the cvs commits and finding
these problems.  I'll probably be releasing 1.0 within the next week, and then
it will be opened up for everyone again.

 Oh well.  You live and learn.  Hopefully, 2.0 will end up being a much smoother
process after learning from these mistakes.