Control: tag -1 moreinfo On Thu, Oct 16, 2014 at 22:12:16 +0200, Kurt Roeckx wrote: > Package: release.debian.org > Severity: normal > Tags: wheezy > User: release.debian.org@packages.debian.org > Usertags: pu > > Hi, > > I would really like to upload new upstream openssl versions from > the 1.0.1-stable branch to wheezy. I've been backporting only the > very important security fixes so far, but there are tons of > important changes I would like to have in stable and general bug > fixes in that branch. There are currently just over 400 commits > between the 1.0.1e version and the current 1.0.1j. I would > actually like to see at least 50% of those commits in wheezy. > > In the 0.9.* series new features got added between the "letter" > releases. Since 1.0, the branches only get bug fixes and other > important changes. This might sometimes include new features like > the fallback SCSV in the latest release, but that is to improve > security. > > This would actually make things for me much more simple. I > sometimes run into problems because of missing bug fixes that have > been done earlier in the branch. And I generaly think that the > 1.0.1j version is much better than then 1.0.1e version. > Is the policy for what gets included in the stable branches described somewhere? What kind of automated or manual regression (or other) testing is done on the stable branches? What rate of changes are we talking about? Cheers, Julien
Attachment:
signature.asc
Description: Digital signature