On 20 July 2012 17:23, Roberto C. Sánchez <[email protected]> wrote: [snip] > Not at all. The version number associated with a change has nothing to > do (or very little) with whether or not it is accepted into testing > during the freeze. It is all about the severity of the bug being > addressed and the extent of the change required to address it. >
OK. >> Or is it that, the Freeze would require you to >> backport fixes to the frozen version? >> > This is only an absolute require if I make new uploads to unstable that > are not targeted for the frozen release. > OK. >> The Fedora shorewall packages bundle all tarballs into a single >> package (and then split them out into sub-packages) - in Debian, are >> you saying you have a package per tarball? If that's the case, I can >> see that you wouldn't want to build a new package for a tarball that >> is unchanged in all but version number. But then, there's nothing >> requiring you to do so. >> > I have one package per upstream tarball. It is possible to combine all > the tarballs into one Debian source package. However, I have thus far > chosen not to do this as it would be complicated if Tom decided to go to > a release scheme where all the components were not always in sync from a > versioning perspective. Yes, this is why I prefer Tom to stick with the current practice :). We could certainly review our packaging process and have a package per tarball, but that (for us) makes updates more laborious, and would involve having the new packages reviewed... not a small amount of work, but not impossible. > Additionally, it makes requesting freeze > exceptions more challenging since it becomes one package with dozens or > hundreds of "gratiutous" changes as opposed do to those changes being > spread out over several packages. > Well, that sounds like shifting the problem more than solving a problem. J. ------------------------------------------------------------------------------ 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
