BugzillaAutoLanding: Difference between revisions

Line 172: Line 172:


==Deployment==
==Deployment==
Go live week of <strike>Aug 8th</strike> and with only logging and watch for issues using live data from actual pushes/db
 
Go live week of December 19th to a small subset of devs (ehsan plus one or two others), watch for issues using live data from actual pushes/db
===TO DO===
* Monitor load & machine resources/wait times
* Monitor load & machine resources/wait times
* Confirm bugs hit from previous attempts are no longer reproducible
* Write up developer documentation on how to use the current system
* Write blog posts and promote the new functionality as well as explaining where this is heading (automated landing across release branches)


As of Sept 20, 2011 we still have not met the projected deployment date for this.  We completed some initial staging in the last week of Marc's internship and the project has been on hold since then.  There are some major bug fixes needed before this can go into a beta period (available to developer usage but not advertised widely).
===Bugs hit===
 
* Double bug posting
Revised timeline:
* Queue messages getting lost
 
* On or before October 15th fix the remaining bugs:
** Double bug posting
** Queue messages getting lost
* Beta running (live in production, unadvertised) on the Try branch only by October 31st


==API==
==API==
Confirmed users
4,467

edits