Zugg MASTER
Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Thu May 01, 2008 10:52 pm
Testing v2.23 this weekend |
As I mentioned in the release notes, I think 2.23 is getting very close to Public status. However, I changed several very low-level routines when fixing some bugs, and it's always possible that this will have unintended side effects.
So what I really need Beta Testers to focus on this weekend is any *new* problems. That is: if something worked in v2.22 and doesn't work now in 2.23, definitely report it with as much detail as possible.
I will be out of the office this weekend (Fri,Sat,Sun), but will still try to look at the forums when I can. On Monday I'll evaluate which bugs are critical to be fixed in the public version and I'll try to release the 2.24 public version on Wednesday. That gives Thursday to apply any "quick fix" that might be needed before I go away to Albuquerque for the next week.
Keep in mind that "Public version" does not mean "Bug-free version". It is impossible for software of the complexity of CMUD to ever be completely bug-free (it's over 1.5 MILLION lines of code, and also uses 3rd party code that might have their own bugs). My intent with Public Versions is to release something that I feel a general user can use for real MUD playing that is stable.
The 2.18 public version had many crashes related to the Settings Editor. The Settings Editor was rewritten in the v2.2x versions, and this should eliminate most of those problems, making this version more stable. I will continue to fix bugs as much as possible, even when adding new features and working on the mapper. But I want to get something better than 2.18 into the Public's hands so that they can use CMUD more reliably for their day-to-day MUDding.
Oh yeah, REMEMBER to make a NEW post for your bug reports, or bump an existing bug report if the problem is listed as being fixed in the Version History but is still broken. Do NOT put bug reports in any reply to this message. And please remember to be as specific as possible when listing a procedure for reproducing a bug. The easier a bug is to reproduce, the better chance it has of getting fixed. |
|