It has been my practice for some time to always upload all of the packages when one of them changes. This includes patch releases such as 4.5.5.3.
You may recall that I originally uploaded only changed packages but that
seemed to cause angst among the user population.
Recent questions from the Debian release team about the current practice
have prompted me to revisit the issue. As I see it, there are three
possible approaches:
1) Continue to release all packages.
2) Continue to release all packages and indicate which of them
actually changed. That would allow individual packagers to release
some or all of them.
3) Only release the changed packages.
We could, of course, have one policy for regular releases and another
one for patch releases.
I welcome all comments and suggestions.
-Tom
--
Tom Eastep \ When I die, I want to go like my Grandfather who
Shoreline, \ died peacefully in his sleep. Not screaming like
Washington, USA \ all of the passengers in his car
http://shorewall.net \________________________________________________
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________ Shorewall-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-devel
