[jbosstools-issues] [JBoss JIRA] (JBIDE-21407) staging/release guides should generate task jiras to remind releng to re-enable disabled jobs once staging or release is done

[Nick Boldt (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-21407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Boldt updated JBIDE-21407:
-------------------------------
    Description: 
Amend both staging and release guides such that disabled jobs are appropriately re-enabled at the correct time: once staging/release announcement emails are sent *if there's a planned future milestone*.

* re-enable job
* set correct github branch
* upversion dependencies (eg., releng scripts)
* upversion target platforms / Central version
* ...?

Verify this is correctly done for 4.3.1.Beta2, as that will also require the same on/off/on steps as were done for 4.3.1.Beta1 (JBIDE-21392).

  was:
Amend both staging and release guides such that disabled jobs are appropriately re-enabled at the correct time: once staging/release announcement emails are sent *if there's a planned future milestone*.

Verify this is correctly done for 4.3.1.Beta2, as that will also require the same on/off/on steps as were done for 4.3.1.Beta1 (JBIDE-21392).



> staging/release guides should generate task jiras to remind releng to re-enable disabled jobs once staging or release is done
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-21407
>                 URL: https://issues.jboss.org/browse/JBIDE-21407
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 4.3.1.Beta1
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 4.3.1.Beta2
>
>
> Amend both staging and release guides such that disabled jobs are appropriately re-enabled at the correct time: once staging/release announcement emails are sent *if there's a planned future milestone*.
> * re-enable job
> * set correct github branch
> * upversion dependencies (eg., releng scripts)
> * upversion target platforms / Central version
> * ...?
> Verify this is correctly done for 4.3.1.Beta2, as that will also require the same on/off/on steps as were done for 4.3.1.Beta1 (JBIDE-21392).



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)