This package has been used for some time by the releases repo,
but installed via extras in setup.cfg. With the switch to not
installing projects to run docs jobs, those now fail due to
missing requirements.
As the first step to get these defined in requirements.txt,
adding to global-requirements and upper-constraints.
* Is the library actively maintained?
Yes, Doug Hellmann is the author and all source is available
on github.
* Is the library good code?
Code is well documented and tested.
* Is the library python 3 compatible?
Yes.
* Is the library license compatible?
Yes, it is using the BSD license.
* Is the library already packaged in the distros we target?
I don't believe so, but this is not a runtime dependency for
any projects. So far, I am only aware of the releases repo
using it for some of our release cycle publishing.
* Is the function of this library already, et cetera?
Nope.
Change-Id: Ib882a4d09898ff206b36ac8aef840bee0748368e
Raven is client for Sentry error tracking tool. It is required
for sentry integration into oslo.log module.
Is the library actively maintained?
Raven is actively maintained (https://github.com/getsentry/raven-python)
Is the library good code?
Code looks good to me, testing via tox included.
Is the library python 3 compatible?
Yes
Is the library license compatible?
Yes (BSD licence)
Is the library already packaged in the distros we target
(Ubuntu latest / Fedora latest)?
Yes, both.
Is the function of this library already covered by other libraries
in global-requirements.txt?
No, as far as it's the only python library to integrate Sentry.
Is the library required for OpenStack project or related dev or
infrastructure setup? (Answer to this should be Yes, of course) Which?
Sentry integration improves develepers experience and allows devs to
collect exceptions and bugs from live environment.
https://review.openstack.org/#/c/518949/https://blueprints.launchpad.net/oslo.log/+spec/sentry-handler
If the library release is managed by the Openstack release process
does it use the cycle-with-intermediary release type?
Raven is 3rd party library, has nothing to do with OpenStack release
process.
Do I need to update anything else?
Nope.
Change-Id: I292b0331a67f238779c8d565c5288d59a34dac69
Rtslib-fb 2.1.64 attempts to update the target dbroot directory
that does not exist on Fedora. This has since been fixed in:
https://github.com/open-iscsi/rtslib-fb/issues/103
Change-Id: I0c8ae37b5f6357850d6302547af15ff4d256595e
Closes-bug: #1737588
The use of loopingcalls seems to have broken in the
Trove (and Heat) gate right when 1.28.1 has been
released.
Partial-Bug: #1738281
Change-Id: I8ad18b54bc9cdacf5bd6ba467a0c46793a50ebbd
Requirements updates needed for new repo for split of in-tree tempest
tests.
Depends-on: I1a8b1be63f20c61ff2817e1202076cc9f177c8a1
Change-Id: I466b98a0645fbac73ad33b52178bcfbef14bfad3
- Actively Maintained?
Yes, this is a very popular Python package and it's maintainer
Adam Hupp is very active within the project.
- Good code?
Looks pretty good to me, currently tested via Travis and the
tox coverage is very comprehensive.
- Python 3 compatable?
Yes, compatible with Python 2.7 and 3.
- License?
MIT
- Packaged as part of targetted distros?
Ubuntu - Yes
Fedora - Yes
- Is the functionality already covered?
This package extends some functionality already provided within
the Python built ins. The Python built in mimetypes simply uses
a files extension to determine MIME type (not very comprehensive)
however python-magic wraps libmagic and provides a much better
method of identifying a files MIME type by using a bunch of
signatures which are compared to parts of the file, and hence
is much likely to return an accurate result.
- Which project is this for?
This is intended to be used as part of the Nemesis project which
aims to provide a file information and intelligence API for the
OpenStack ecosystem. However I can imagine this would be useful
for any project which needs to identify the type of a file with
some accuracy.
Change-Id: I1382d1cd22275b03e3f0c6aff941d1c207e37faa
The oslosphinx library is deprecated, so we don't need to sync
requirements to it any more. If we do need a release for some reason, we
can update the requirements by hand or just leave the minimums as they
are.
Change-Id: I296c212aa342cc022ba026ba29019bb3dae9c1d0
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Change-Id: If69bdee2e78589773d25c1d5ccdc3122bd9ec431
meta:version: 3.3.0
meta:diff-start: -
meta:series: queens
meta:release-type: release
meta:pypi: yes
meta:first: no
meta:release:Author: Jay S. Bryant <jungleboyj@electronicjungle.net>
meta:release:Commit: Jay S. Bryant <jungleboyj@electronicjungle.net>
meta:release:Change-Id: I1be2fb00f99970d77889b8333d50ca818f150a91
meta:release:Code-Review+2: Sean McGinnis <sean.mcginnis@gmail.com>
meta:release:Workflow+1: Sean McGinnis <sean.mcginnis@gmail.com>
