On 19 July 2012 10:31, Tom Eastep <[email protected]> wrote: > 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. >
With my Fedora packager hat on, I'd prefer one of the above. > 3) Only release the changed packages. > This just gets more fiddly and error prone in my opinion. Keeping all tarball versions in lock step is easy for boneheads like me to follow. J. > 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 \________________________________________________ > > > > ------------------------------------------------------------------------------ > 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 > ------------------------------------------------------------------------------ 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
