Tony Breeds Requirements candidacy for Ocata
Change-Id: I33f442f6fb5ea8210a09b06ad920acd62d15405a
This commit is contained in:
parent
59e4294f09
commit
e38bff5e5d
23
candidates/ocata/Requirements/tonyb.txt
Normal file
23
candidates/ocata/Requirements/tonyb.txt
Normal file
@ -0,0 +1,23 @@
|
||||
I'd like to continue to serve as the OpenStack Requirements PTL.
|
||||
|
||||
Since the Austin summit the requirements team has worked to reduced tech debt
|
||||
and improve gating of constraints updates. This has reduced the number of
|
||||
fires after new OpenStack library updates. We still have several items in
|
||||
front of us. Continuing with the themes for my recent election:
|
||||
|
||||
In rough priority order:
|
||||
- Improving communication, often decisions are made in the requirements team
|
||||
that affect many projects, I have a commitment to bringing more experts in
|
||||
for strategic reviews/discussions
|
||||
- Understand how we can work with/enhance pip tooling to create a more
|
||||
satisfactory requirements/constraints experience for OpenStack
|
||||
- Work closely with the release managers as there is still a lot of common
|
||||
issues there. In that a release of $project will trigger processes in the
|
||||
requirements team.
|
||||
- Getting openstack_requirements *code* to the point it can be installed as a
|
||||
library. We've seen issues in the past where stable branches need largish
|
||||
backports to work correctly. Really the *code* and *data* should be treated
|
||||
independently
|
||||
- Testing lower bounds of our supported requirements [lower-constraints.txt]
|
||||
|
||||
If the team and community will have me I'm happy to serve again.
|
Loading…
Reference in New Issue
Block a user