micro release exception for LibreOffice

[Martin Pitt]

Hello Bjoern,

Bjoern Michaelsen [2012-06-01 12:07 +0200]:
> I would like to apply for a micro release exception for LibreOffice.

In general I think it does make sense to use the new upstream
microreleases, to benefit from their QA process and from the testing
that happens in PPAs. However, I still have some concerns/questions:

Is there a written policy what kind of changes are permitted in
stable upstream branches? How does that compare to our SRU policy?

We did have more than one attempted LibO (and OO.o back then) SRU
which never made it to -updates because the new microrelease
introduced a regression (e. g. #919659, #623267). Can we do, or have
there been, policy changes or test improvements to prevent these?

How we make sure that the changes also work on ARM platforms?

What is the main motivation to ask for a MRE? Are there usually/often
too many changes, or fixes which do not have corresponding LP bugs to
verify them individually? Or do the stable branches get new
features, UI changes, or invasive changes which carry a high risk of
regressions?

Thanks,

Martin

-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <https://lists.ubuntu.com/archives/technical-board/attachments/20120605/fc9a716d/attachment.pgp>