Am Dienstag, 22. März 2005 08:43 schrieb Michael D Schleif: > kp => > > Again, please understand, I am new to Bering-uClibc, and to > Shorewall. > > * "K.-P. Kirchdörfer" <[EMAIL PROTECTED]> [2005:03:22:08:26:22+0100] scribed: > > Michael; > > > > you can always download shorewall-[version].lrp from shorewall > > mirrors to use and test the latest and greatest. > > O, so Shorewall is supplying shorwall.lrp, and *NOT* the > Bering-uClibc team? > > Again, I am not so much interested in testing as I am in securing > my clients' networks. Hence, my subject phrase "philosophy" . . . > > > Note that shorewall 2.0.15 has been released in January - so it's > > not that old one might think looking only at the version numbers. > > <snip /> > > Yes, two (2) dot versions higher seized my curiosity. How -- and > more to the point, WHY -- go from 2.0.x to 2.1.x and to 2.2.x in > less than three (3) months? >
It's the shorewall release model... kp From shorewall.net: "Even numbered major releases (e.g., 1.4, 2.0, 2.2, ...) are Stable Releases. No major new features are added to stable releases and new minor releases of a stable release will only contain bug fixes and simple low-risk enhancements. Installing a new minor release for the major release that you are currently running involves no migration issues unless you want to take advantage of an enhancement (for example, if you are running 1.4.10 and I release 1.4.11, your current configuration is 100% compatible with the new release). Support is available through the Mailing List for the two most recent Stable Releases. Odd numbered major releases (e.g., 2.1, 2.3, ...) are Development Releases. Development releases are where new functionality is introduced. Documentation for new features will be available but it may not be up to the standards of the stable release documentation. Sites running Development Releases should be prepared to play an active role in testing new features. Bug fixes and problem resolution for the development release take a back seat to support of the stable releases. Problem reports for the current development release should be sent to the Shorewall Development Mailing List." kp ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click ------------------------------------------------------------------------ leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
