Skip to content

Latest commit

 

History

History
30 lines (19 loc) · 2.04 KB

code_freezes.adoc

File metadata and controls

30 lines (19 loc) · 2.04 KB
Raw

Code Freezes

Before every milestone, a code freeze is declared. This is to ensure that everyone has time to perform the following steps:

  1. Cleanup unresolved JIRAs set for the upcoming milestone

  2. Upversion their plugins and features, if they haven’t already done so

  3. Build their latest code with the most recent parent pom, updating their root pom if necessary

  4. Build their latest code with the most recent target platform(s)

  5. Run tests using the most recent target platform(s)

  6. Branch (or tag) their code so there’s a stable version of the code to feed into the Jenkins job cascade

  7. Communicate readiness to the mailing list or via JIRA so that program management and release engineering is aware

How do I remember all that?

Generally these steps are provided within a Task JIRA, sent to all project leads the night before the Code Freeze date.

Here are some examples from past freezes:

Task JIRAs are generated using the createTaskJIRAs.py script [1]. The script can be used for all kinds of Task JIRAs.

When is the next Code Freeze?

1. Don’t have permission to view the script? You can request access here.