Tom Eastep wrote: >Shortly after I release Shorewall 3.4.2, I will be issuing the first release >of the new development thread which I'm calling Shorewall4. > >I'm announcing the new product ahead of time so that people will have a >chance to comment on the approach (and the product name) in advance of the >initial release. > >Shorewall4 is going to be a companion product to Shorewall. It will include >a new compiler, written entirely in Perl. > >Shorewall4 depends on Shorewall (3.4.2 or later). So if you want to use the >new compiler, you must install both Shorewall and Shorewall4.
I've been thinking about this on and off, and one twisted logic process says you should call the new package Shorewall2 ! At the moment we have 'Shorewall' version 3.4.2, the new package would be 'Shorewall2' version 1.<something>. I don't think that would be any less confusing than between Shorewall4 and Shorewall version 4 should the current version get a major update. I can think of a few commercial packages that have done something similar - going from 'X version 2.3' to 'X2 version 1.0'. Better would be to avoid numeric suffixes that can be confused with version numbers, and if you don't like '-ng', how about '-new' ? shorewall-new in the same way as we have amavis-new. new-shorewall (or any other prefix) would be bad as it then wouldn't sort adjacent to shorewall when browsing package lists. ------------------------------------------------------------------------- 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 _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
