-
Notifications
You must be signed in to change notification settings - Fork 176
Creating a maintenance branch
But Narayana provides some maintenance branches as well (4.17
, 5.9
, 5.11
, …). This wiki documents steps which are needed when a new maintenance branch is created.
-
Only
narayana
repository should be released. Remove all other repositories from the release plan (e.g.quickstart
,performance
, …). See the PR at https://github.com/jbosstm/narayana/commit/bac79b25ec013f6d19e476323bdbe3ccf0ca5418 -
change the
pre-release-vars.sh
script (https://github.com/jbosstm/narayana/blob/5.10.5.Final/scripts/pre-release-vars.sh#L1) for theBRANCH
contains the name of the maintenance branch which is created -
Remove generating of the web pages for the maintenance branch. The
ant
command should avoid theweb
target. See how the script may be adjusted here https://github.com/jbosstm/narayana/commit/a155fa429ab8db18f555048be65bd73b9dfca6fa -
Change the narayana-rebase.sh script to define the environmental variable
BRANCHPOINT
with value of the branch. -
Change the branch-names.sh script to refer to WildFly maintenance branches in jbossts/jboss-as repository.
-
Change the narayana.sh script (function
build_as
orclone_as
) which clones the WildFly maintenance repository to point to correct branch in context of the Narayana maintenance branch (e.g.5_9_BRANCH
or5_11_BRANCH
) and change thegit rebase
to work against appropriate WildFly branch (e.g.18.x
or23.x
). -
Verify the content of the
build-release-pkgs.xml
to contain the correct value of thetag
property. -
Create the maintenance branch (of the same version) for jbosstm quickstarts (https://github.com/jbosstm/quickstart/) as well. The quickstarts are verified by QE and they need a branch to work with.
-
Make sure autoReleaseAfterClose is set to false in root pom.xml. In fact maintenance branches are not supposed to be released to Maven Central, but only tagged and pushed to GitHub.