From version < 88.1 >
edited by Eduard Moraru
on 2020/01/07 16:57
To version < 89.1 >
edited by Eduard Moraru
on 2020/01/07 16:59
< >
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -35,8 +35,7 @@
35 35  
36 36  * (x) Verify that no tests are failing [[on the CI Server>>http://ci.xwiki.org]] (or that failures are understood, see [[known flickering tests>>https://jira.xwiki.org/issues/?filter=14240]], don't forget to update the dates of last seen flickers).
37 37  * (x) [[Verify>>ReleasePlans.ReleasePlanHelp||anchor="HInitialBackwardCompatibilityCheck"]] that the {{scm project="xwiki-commons" path="pom.xml"}}${escapetool.H}${escapetool.H}xwiki-commons${escapetool.H}${escapetool.H}'s top level POM{{/scm}} has a ${escapetool.H}${escapetool.H}xwiki.compatibility.previous.version${escapetool.H}${escapetool.H} property correctly pointing to the latest stable (non-milestone) release and if not, change it.
38 -* (x) Verify that there are no [[JIRA issues that are still open, even if they have commits>>https://jira.xwiki.org/issues/?jql=category%20%3D%2010000%20and%20(labels%20is%20empty%20or%20labels%20not%20in%20(%22flickering%22))%20and%20resolution%20%3D%20Unresolved%20and%20issue.property%5Bdevelopment%5D.commits%20%3E%200%20and%20updated%20%3E%20%22$datetool.format('yyyy-MM-dd', $previousRCReleaseDate)%22]]. Such open issues may exist because the wrong issue key was used when committing, the commit is just trying to fix a test or adding extra logging (and not affecting the runtime) while the problem has not been addressed, it's a commit in a feature branch, etc. You need to ignore these false positives and detect any issue that has actual work done on it that is relevant for this release, close it and assign it the correct fix version so that it's properly counted in the release notes.
39 -** Note: The JIRA query is not perfect yet as we [[cannot query on the commit update date>>https://jira.atlassian.com/browse/JRASERVER-64130]]. Thus FTM you'll need to review each issue listed and verify if the issue should be closed or if it's a false positive.
38 +* (x) [[Verify>>ReleasePlans.ReleasePlanHelp||anchor="HVerifyissueswithcommits"]] that there are no [[JIRA issues that are still open, even if they have commits>>https://jira.xwiki.org/issues/?jql=category%20%3D%2010000%20and%20(labels%20is%20empty%20or%20labels%20not%20in%20(%22flickering%22))%20and%20resolution%20%3D%20Unresolved%20and%20issue.property%5Bdevelopment%5D.commits%20%3E%200%20and%20updated%20%3E%20%22$datetool.format('yyyy-MM-dd', $previousRCReleaseDate)%22]].
40 40  * Make sure next version exists on [[jira>>https://jira.xwiki.org]] projects (JIRA releases are done automatically in the build):
41 41  ** (x) [[Commons JIRA>>https://jira.xwiki.org/plugins/servlet/project-config/XCOMMONS/versions]]
42 42  ** (x) [[Rendering JIRA>>https://jira.xwiki.org/plugins/servlet/project-config/XRENDERING/versions]]

Release Date:
Released by:

Failed to execute the [velocity] macro. Cause: [null]. Click on this message for details.

Get Connected