MailScanner ANNOUNCEMENT: Release schedule change

[Dave Shariff Yadallee - System Administrator a.k.a. The Root of the Problem]

On Mon, May 22, 2006 at 10:25:10AM +0100, Randal, Phil wrote:
> Julian,
> 
> Because of the various problems with 4.53, do you have any plans to
> release 4.54 as a stable release soon to ensure that people aren't still
> running 4.53?  If I recall correctly, 4.53.8 still had a bug in the
> phishing code which was stripping out stuff it shouldn't have.
> 
> We've been running 4.54.2 here without problems since its release.
> 
> Cheers,
> 
> Phil
> ----
> Phil Randal
> Network Engineer
> Herefordshire Council
> Hereford, UK  
> 
> > -----Original Message-----
> > From: mailscanner-bounces at lists.mailscanner.info 
> > [mailto:mailscanner-bounces at lists.mailscanner.info] On Behalf 
> > Of Julian Field
> > Sent: 20 May 2006 22:50
> > To: MailScanner discussion; MailScanner Announcements List
> > Subject: MailScanner ANNOUNCEMENT: Release schedule change
> > 
> > MailScanner is now a pretty mature application. It has undergone 
> > continuous development for about 6 years and has come a long 
> > way in that 
> > time.
> > 
> > Version 1 was 1,200 lines of Perl and shell, and had about 15 
> > configuration options.
> > Version 4.54 is over 44,000 lines of Perl and shell, and has 343 
> > configuration options.
> > 
> > These days, virtually all of the new features are written 
> > specifically 
> > for a few people, and are not desperately needed by most users.
> > 
> > As a result of this, and to allow more time for testing, I am 
> > going to 
> > change the normal release schedule to a new stable release every 2 
> > months instead of every month. Due to the nature of the 
> > world, I reserve 
> > the right to release every month or two months as I choose. 
> > The latest 
> > stable version number is always posted at the top of the home page of 
> > the www.MailScanner.info website.
> > 
> > This will be good for MailScanner as it will be tested better before 
> > release, and it will be good for me by reducing the time I 
> > have to spend 
> > in the run-up to the start of every month.
> > 
> > Note: This will not affect important bug-fix releases at all.
> > 
> > Serious problems in the latest stable release will still be fixed as 
> > soon as possible, and published as soon as they have been 
> > fixed. These 
> > may be released either as later stable releases or early betas of the 
> > next release, as I do not want to have to fork the source 
> > code database 
> > at the start of every month and maintain two copies of the 
> > source code. 
> > Due to the extra time available for testing, this problem will be 
> > drastically reduced anyway.
> > 
> > I hope you all understand my reasons for making this change, 
> > and that it 
> > will also reduce the time some of you spend maintaining your 
> > MailScanner 
> > systems at the very latest version.
> > 
> > Maybe you would like to be in the "inner circle" of official 
> > beta-testers. I might even print a special T-shirt for you with your 
> > company logo on it advertising that you are a member of the 
> > inner circle.
> > 
> > Please read my other posting re beta testers.
> > 

While we are at it, where is the latest beta?

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.