Confirmed users
2,456
edits
User:Catlee/SchedulerDB: Difference between revisions
→Timeline
| Line 54: | Line 54: | ||
= Timeline = | = Timeline = | ||
* March 1st- | * March 1st-26th | ||
** deploy new python, twisted toolchain on staging master | ** deploy new python, twisted toolchain on staging master | ||
** deploy current buildbot tip on staging master and slaves, start testing current patches (see test cases to exercise above) | ** deploy current buildbot tip on staging master and slaves, start testing current patches (see test cases to exercise above) | ||
* March | * March 29th-April 2 | ||
** deploy new python, twisted toolchain on talos staging master | ** deploy new python, twisted toolchain on talos staging master | ||
** deploy current buildbot tip on talos staging master and slaves, start testing current patches | ** deploy current buildbot tip on talos staging master and slaves, start testing current patches | ||
| Line 65: | Line 65: | ||
** would only backport to 0.7.12 if 0.8.0 takes too long to release | ** would only backport to 0.7.12 if 0.8.0 takes too long to release | ||
* April | * April 5-7 Deploy buildbot 0.8.0 on staging build/unittest master | ||
* April | * April 5-7 Deploy buildbot 0.8.0 on staging talos master | ||
* April | * April 12 Deploy buildbot, python, twisted onto production build masters and slaves | ||
** Slave upgrade isn't strictly necessary to do, but feels right thing to do. | ** Slave upgrade isn't strictly necessary to do, but feels right thing to do. | ||
*** has the potential to break builds (if e.g. part of build doesn't work with python 2.6). If needed, we could isolate build tools from system tools. | *** has the potential to break builds (if e.g. part of build doesn't work with python 2.6). If needed, we could isolate build tools from system tools. | ||