Jenkins Jobs created and triggered for build!
Achterdiek 19, D-28357 Bremen
From: jim ferenczi [mailto:firstname.lastname@example.org]
Sent: Saturday, January 14, 2017 4:03 PM
Subject: Re: 6.4 release
2017-01-14 16:01 GMT+01:00 Uwe Schindler <email@example.com>:
Thanks! I will update Jenkins this evening (Policeman and ASF).
The first successful Java 9 build 152 was executed already on branch-6x, so we are in good shape also on Java 9 front. 😎
Am 14. Januar 2017 15:57:13 MEZ schrieb jim ferenczi <firstname.lastname@example.org>:
The release branch for 6.4 is pushed so the feature freeze phase has officially started.
I don't have an admin account on Jenkins so any help would be appreciated. We need to copy the job for the new branch.
No new features may be committed to the branch.
Documentation patches, build patches and serious bug fixes may be committed to the branch. However, you should submit all patches you want to commit to Jira first to give others the chance to review and possibly vote against the patch. Keep in mind that it is our main intention to keep the branch as stable as possible.
All patches that are intended for the branch should first be committed to the unstable branch, merged into the stable branch, and then into the current release branch.
Normal unstable and stable branch development may continue as usual. However, if you plan to commit a big change to the unstable branch while the branch feature freeze is in effect, think twice: can't the addition wait a couple more days? Merges of bug fixes into the branch may become more difficult.
Only Jira issues with Fix version "6.4" and priority "Blocker" will delay a release candidate build.
Achterdiek 19, 28357 Bremen