> > I'm a fan of frequent releases. Smaller changes each time is a good > > thing. Both from a user and a sysadmin point of view.
In principle this is a great idea. Can I suggest a minor variant? Frequent releases benefit sites that are capable of experimentation. Enterprise deployments don't move so quickly, so I'd suggest you designate two tracks: a "development" track (release early and often) and a "stable" track that's a little more conservative (release on a regular, planned schedule, order of once or twice a year, unless there's something major). This would help the folks offering support a great deal. Tens of thousands of client machines would thank you.. 8-) ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
