[ https://issues.jboss.org/browse/JBIDE-21392?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21392: ------------------------------------ To Max's point about being surprised that jobs get disabled, it's all part of the staging for QE process so that we don't accidentally overwrite a stage-in-progress: https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... But that said, I should probably add a note to the RELEASE docs [1], [2] to ensure that we re-enable them (as appropriate) once a release is complete. [1] https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... [2] https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... Problem arises that the release guide ends when the email templates have been sent to the project manager for the "... is available!" email announcements. So I would still need to remember to go back into the guide AFTER all my stuff is done and after all Alexey/Chris/Len/PaulRobinson's stuff is done. Almost need a post-release-prep-for-next-milestone guide, or even better... ... to generate a task jira as part of the staging/release process to remind me to not only re-enable jobs, but to set the correct github branches & other job parameters too: JBIDE-21407. -- This message was sent by Atlassian JIRA (v6.4.11#64026)