On Tuesday 26 June 2007 18:19, Tom Eastep wrote:
> It has been my intention to continue the beta period for 4.0 through the
> summer and to release 4.0 in the September time frame. Several factors have
> caused me to rethink that schedule.
>
> - The rate of problem reports against Shorewall-perl has dropped rapidly
> and the code seems to be quite stable.
> - The 4.0 Documentation has come together more quickly than I had planned.
> - 3.4 and 4.0 are now on nearly identical code bases except for
>   Shorewall-perl. I have patch files to make up for the differences so it
> is now possible to make maintenance updates to 3.4 and roll those updates
> into 4.0 with almost no additional effort.
>
> In light of these factors, I'm thinking of producing one more 4.0 Beta
> release then releasing 4.0.0 RC1. Assuming that the release candidate
> doesn't encounter problems, I would anticipate final release some time in
> late July or early August.
>
> Because supporting 3.4 will not present any burden over supporting 4.0, I
> plan to break the "two supported releases" rule and to support 3.2, 3.4 and
> 4.0 until 4.2 comes along.
>
> Comments?
>
> -Tom

Tom

My testing over the last few weeks suggests that your revised schedule is 
appropriate. There is a possible issue with the 'shorewall add' command. I am 
still testing this, and will report back anything I find. Other than that 
Beta 6 is proving to be very stable.

I have also done some testing against iptables 1.3.8. and haven't encountered 
any problems so far.

As iptables 1.3.8 now supports the randomising of source ports on snat, same, 
and masq rules, would it be a good idea to include support in Shorewall 4.0 
or wait until 4.2?

Steven. 




-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Shorewall-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-devel

Reply via email to