John wrote in SF Bug #517267: > Has AOLserver 3.x been abandoned in terms of maintenance releases? > It's my impression that 4.x isn't stable, especially given that > critical modules (well, nsopenssl at least...) are still considered > "beta" in their AOLserver 4.x incarnations. And of course AOL is > still using 3.4.2.
This is a great question. How long should we support the 3.x release? The 4.0 tree is already up to 4.0.5 with 4.0.6 just days away. The 4.0 tree has been considered stable and production-ready for a while now, but as John points out, AOL has been slow to upgrade all its servers to 4.0. While I'm not terribly enthusiastic about the idea, I'm okay with backporting significant bug fixes to 3.x. However, I am against the idea of fulfilling any RFE's in 3.x -- the 3.x tree at this point should be considered feature-frozen and no new features will go into it. Basically, the 3.x release is officially in support and maintenance mode, and new development will should only be done in the 4.x tree. How do others feel about this? Are there other bugs that need to be fixed in 3.x, other than #517267? (Including the ones fixed in 4.x that haven't been backported to 3.x yet?) -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70) -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
