Confirmed users
194
edits
User:Zeller: Difference between revisions
Jump to navigation
Jump to search
→Notes
(→Notes) |
|||
| Line 3: | Line 3: | ||
==== Notes ==== | ==== Notes ==== | ||
* /status - Lists all available releases, that have status data, in JSON format and can be queried with parameters (ie /status?var1=1&var2=10). Analogous to /releases | * /status - Lists all available releases, that have status data, in JSON format and can be queried with parameters (ie /status?var1=1&var2=10). Analogous to /releases | ||
* / | * /statuses.html – Pretty GUI view of the info shown in /status. Analogous to /releases.html | ||
* /status/<release-name> | * /status/<release-name> | ||
** GET: Lists release status info in JSON. Analogous to /releases/<release-name> | ** GET: Lists release status info in JSON. Analogous to /releases/<release-name> | ||
** POST: covered in Bug 1032985 | ** POST: covered in Bug 1032985 | ||
* /status/.html – Pretty GUI view of the info shown in /status/ GET, possibly including a visual timeline of the 6 steps: Tagging completed, All builds/repacks completed, Updates on betatest, Ready for releasetest, Ready for release and Postrelease. (status steps taken from Bug 826753 comment 0) | * /status/<release-name>.html – Pretty GUI view of the info shown in /status/ GET, possibly including a visual timeline of the 6 steps: Tagging completed, All builds/repacks completed, Updates on betatest, Ready for releasetest, Ready for release and Postrelease. (status steps taken from Bug 826753 comment 0) | ||
==== Questions ==== | ==== Questions ==== | ||
* Why does /release 404? | * Why does /release 404? | ||