MRE for juju-core/juju-mongodb

James Page james.page at ubuntu.com
Tue Apr 15 10:03:47 UTC 2014


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 15/04/14 07:56, Martin Pitt wrote:
>> https://bugs.launchpad.net/ubuntu/saucy/+source/juju-core/+bug/1277526
>>
>>
>> 
is being worked on - in your opinion, do the fixes being included meet
>> the requirements for a normal SRU?
> 
> For updates of that kind, a MRE exception is definitively
> required. Bugs like #1257481 are of course fine for normal SRUs
> (and even essential to backport), but it also has a lot of new
> features like #1254729 or #1268913 which aren't covered by the
> uusal SRU policy and thus need an exception.
> 
> My gut feeling is that provided enough testing (automatic or
> manual), this looks like an adequate SRU for an LTS. I think it's
> too intrusive/too much work for saucy as that's not an attractive
> server platform and will go EOL in 3 months anyway, but I'd be okay
> with going through that exercise as a kind of test run for this
> MRE request.

My thinking as well - I've been trying to use the 1.16.x series on
saucy as drill practice for a LTS release to get both the server team
and upstream juju-core into a common understanding of how the process
should work.

> All individual bugs have been prepared with the SRU info and test 
> cases, yay for that!

Yup - just finished up those so that we can push onwards with this SRU
and hopefully help support the MRE request.

I'll also have an update for juju-mongodb shortly after release;
2.4.10 was released last week with a few important bug fixes.

Cheers

James

- -- 
James Page
Ubuntu and Debian Developer
james.page at ubuntu.com
jamespage at debian.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJTTQQDAAoJEL/srsug59jDGN8P/jIIXoRq5Og2MdTSvmuc+Y6e
oVYYFwBCCf08GO8xmaXqMq7J8LKXjBNSA8hJptQ2dR267C4rVKGJoG1B3xpbE/N+
cQn/LZiOTFL7JwA2xshuoApts0h7oMSLSRAZezCBRH+8vr1MAfh/dHGTDmhFvlHr
oCpMKB4KqNXvoThosg2c/ABjhfVMCQsWsmHZVSCS7r31k4EFMN/MbGnW7ImH4jt9
NMr7ZP1HdAv+jvw7Di35dcY+YdVuvVaf5jKJ+z3qox+vhmsVjOb6GaoqZnX1WA+c
QEFIEMJ2Hz9g6VgzPxl6sD+rgm1gpmzr3yqUaoDpc0/HiNtgF8JRCiWmDlAe1/BR
Ejb2lFvWh2FMistj9xT/BqSoEcy6zlGPBcSm6Lcs0zf5Mq9pOh+w1nQC7b1SQipB
k2gdNOxi19iUXgSj4tqFXJwaSnBpHuSdNFuSsRiQpYjpWiK7kQWAeViJJTZeNie3
1kpdNGYP/GAFuCAz5Ell+X6Qe3Kkh/TLseIacFvrreS3SQEIHE7w7RDIuINMJwaI
RTwJq0NwRS8X8YzNWrro+a/auqSmRimrEsaNzfPdMwvyKsVRrs6HZJs2dCNELgV+
JUioMvxxbIItoKPBTNh2zsIpCHyG7X6NjQcj+CdTIXy1qk4x2JkStG6rztlxBiWC
vNboOGnJd/yjVvGVat/v
=EyFL
-----END PGP SIGNATURE-----



More information about the technical-board mailing list