Uploaded image for project: 'Quarkus Documentation'
  1. Quarkus Documentation
  2. QDOCS-497

Create the quarkus-3-2 branch when we are almost ready for doc freeze

XMLWordPrintable

    • 2
    • False
    • Hide

      None

      Show
      None
    • False
    • Quarkus Docs Sprint 15

      Scope of this task:

      As close to the final commit as possible for the 3.2 downstream release, so after the GA deadline, JIRAs are verified by QE and before the pre-publishing needs to start...

      1. Collaborate with QDOCS team that the branch off is happening, in case of last minute commits.
      2. In the main Quarkus GitLab repo, create a new branch called `quarkus-3-2`, which is in the repo upstream, not your local or remote fork.
      3. Go to Code>Commits and make sure that the commit history  of your branch `quarkus-3-2` is identical to the commit history of `main`.
      4. Go to Settings>Repository>Protected Branches and select `quarkus-3-2` branch.
      5. Select the option to protect `quarkus-3-2`
      6. Ask a colleague to verify that the branch looks good and do some spot checks on the content, especially late content changes.
      7. Edit the pantheon2.yml file in the root of the 3.2 branch and change line 3 from main to the name of the 3.2 PV2 project. Make sure that there are no spaces or extra linebreaks added.
      8. Commit the change to upstream/quarkus-3-2.

       

      Note: In step 2-4, you could use the git command line and TIG. This is another way.

      The branch is now ready for git import from PV2 to this project:

       

              mmaler@redhat.com Michal Maléř
              mpurcell@redhat.com Michelle Purcell
              Sheila Jones
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: