MRE: OpenStack Oslo libraries
James Page
james.page at ubuntu.com
Tue Jun 23 16:11:52 UTC 2015
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi TB
Alongside the core OpenStack packages already covered under a MRE for
stable updates, I'd like to include all of the Oslo libraries used by
these packages.
Oslo is the shared library project for OpenStack, promoting re-use of
common code via python modules rather than code-syncing.
For each OpenStack release, a specific set of Oslo library versions
are identified as associated with the OpenStack release; branches are
maintain upstream in the same fashion as for core OpenStack projects
(stable/kilo for example).
In terms of testing, we'd undertake the same testing we apply to core
OpenStack packages for any updates into these libraries; only patch
level releases would be covered under the MRE - for example:
https://bugs.launchpad.net/ubuntu/+source/oslo.messaging/+bug/1467959
upgrades 1.8.1 -> 1.8.3 for Ubuntu vivid. The current list of Oslo
packaging includes:
python-oslo.concurrency
python-oslo.config (oslo.config < wily)
python-oslo.context
python-oslo.db
python-oslo.i18n
python-oslo.log
python-oslo.messaging (oslo.messaging < wily)
python-oslo.middleware
python-oslo.policy
python-oslo.rootwrap (oslo-rootwrap < wily)
python-oslo.serialization
python-oslo.utils
python-oslo.versionedobjects
python-oslo.vmware
I don't expect the frequency of patch releases to be large; typically
there are a flurry post release day, and then things settle down.
Thanks for taking the time to consider this MRE request!
Regards
James
- --
James Page
Ubuntu and Debian Developer
james.page at ubuntu.com
jamespage at debian.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJViYVHAAoJEL/srsug59jDaT8QAJR8cel9QfzfnZKC0fWJiPUn
7+16qSj3ml2HexSV0hnO3kFgX38I5IOwlT9tKl2cRMLbPL/i9kfa3rzuaUfwo9Md
5oA/7s8HaroDCrg6MKVRB0/OVdQ9W+nsT0NqaOMNDUvABMmh65yr/R6sCd79haMW
A9dr3FSwtRLfOfEXaPSe0YsiVOcMtqAD5q7aQp9scs3wnHqrAmPLXpU650yV3KlC
pxcIW2O99BGdPq14wFd2BB3iSfgDfss1nk1+jtrb1CP2zBns5HKsQV/Rz1Y+/giO
Ja7ggnxi82l1L+/uRsOG5pEk8/GCMveY3SpNPDN9FAfOwhttDWrLCqKNUUhgClMi
FTi7/IETpNyMIkWfFdOHFSZAYITjW7tP5wdMae0t6ADutUYq/alCIE4wyqC1fjFr
enNuKrVRxfAWBEaf8Zj7rQjZiCB+TbwzC2rx6tJPMpVYWRccYggOMdzd4ucGd2+f
CIhPxQteWn1VraASI+dw6Q5rVKEjz8+i4A34SVxidKL5GCfyB5h98hs0PCwVRMJp
k/K1TosgyCRS7MgDnCugaBE0z7qDxl1eOqRYxrEy1ymAyyDerfCBuT/KekxW1mVz
Z3KU5G3lccz0pJjrgyFJEDLjWpCSx921X/TUA9BEzdNnqkUleEeo5CgLRfe4Tts0
pWi5veSmHZqaZtjLQDsN
=j6tV
-----END PGP SIGNATURE-----
More information about the technical-board
mailing list