On 06/20/2017 07:26 AM, Bruno Friedmann wrote:

> Hi Tom, as package maintainer for openSUSE, I've one question.
> We have a product line called Leap on which we try to minimize the changes an 
> end users can have to deal with.
> So the last two version 42.1 and 42.2 I've stick to 4.6.13 series.
> 
> Now in one month we will have 42.3 released, and I wonder if I should 
> continue 
> to be hard conservative and keep 4.6.13 or move the package to something 
> never 
> ?
> 
> As there's configuration migration to be done, I'm a bit reluctant as I don't 
> know how complex configuration end-users (normally admins) have setup.
> 
> On my side, I've successfully updated simple setup just with shorewall update 
> -a so I would say that nothing is really hard complicated right ?
> 
> Actually I've 5.1.4.3 packaged and ready for submission, if you tell me that 
> better for users to go for this version, then I will follow your advise.

Hi Bruno,

Migrating from 4.6.13 to 5.1.x is straightforward using 'shorewall
update -a'. I think that it important, however, to alert users that this
step is required, so that there isn't a lot of surprise and confusion
during the distribution upgrade. I am aware of one distribution that
actually runs 'update -a' as part of the RPM update process so that
users need not be aware of this requirement.

Does Leap have a mechanism to alert users when a release includes a
change that requires an additional conversion step?

-Tom
-- 
Tom Eastep        \   Q: What do you get when you cross a mobster with
Shoreline,         \     an international standard?
Washington, USA     \ A: Someone who makes you an offer you can't
http://shorewall.org \   understand
                      \_______________________________________________

Attachment: signature.asc
Description: OpenPGP digital signature

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users

Reply via email to