Open bwbarrett opened 1 year ago
Is there a timeline for a 4.1.7 release? I am hanging out for it to be released so we can deploy with the #12141 fix :)
@bwbarrett and I were literally talking about this earlier today. We hope to get the first steps done towards release later this week.
NOTE: The Open MPI v4.1.x branch was created after v4.0.5. Hence, for some of the
git log ...
commands, thelast_release_tag
should probably bev4.0.5
.Build the Release
VERSION
c:r:a
shared library version number(s) inVERSION
per the GNU Libtool shared library version number rulesgit checkout BRANCH; git pull --rebase; git log --stat --topo-order --decorate TAG_FROM_PREVIOUS_RELEASE..HEAD
to examine the Git logs and see what has changed.vx.y.z
wherez>1
), you probably want to examinegit log --stat --no-merges last_release_tag..this_branch_name
to see what source code files have changed (which directly impacts how to increment thec:r:a
values).vx.y.0
), setr
to 0 and increasec
values by 10 compared to the first release in the prior series (i.e.,vx.(y-1).0
orv(x-1).0.0
, as relevant).vx.y.0
, wherey>1
), seta
values to 10 so that the shared libraries will be ABI compatible with the prior release series.vx.0.0
), seta
values to 0 so that there is no possibility of users accidentally mixing shared library versions.README
: all relevant updates, build options, etc. Be sure to update the date near the top of the file.NEWS
: List all user-noticeable changes. Similar to setting shared library versions (above):vx.y.z
wherez>1
), you probably want to examinegit log --stat --no-merges last_release_tag..this_branch_name
to see what has changed.vx.y.0
wherey>1
, or this isvx.0.0
), you will need to be more creative in examining the git logs because this release is on a different branch than the prior release (vx.(y-1).z
). Hence,git log ... last_release_tag..this_branch_name
will not necessarily give you need. You may need to merge what has changed on your branch with what has changed on the prior release branch, depending on when the prior release branched from this branch. Read the SPECIFYING RANGES sectiongitrevisions(7)
for more details.LICENSE
: Update the years in the copyright noticesPublish pre-releases
git tag -a v3.0.1rc1 <HASH>
). Verifysoftware/ompi/vCURRENT_RELEASE software/ompi/version.inc
ompi-www
, wait for it to show up on the web site (might take up to 30 minutes?)devel@lists.open-mpi.org
andompi-packagers@lists.open-mpi.org
mailing lists announcing the pre-releaseMake the release tarball
git tag -a v3.0.1 <HASH>
). VerifyPublish the release
cp -r software/ompi/vCURRENT_RELEASE software/ompi/vRELEASE
(where RELEASE is for the new release X.Y and CURRENT_RELEASE is the X.Y of the current release)timeline-graph.php
to indicate relevant dates, such as branchingversion.inc
to remove the "existing" versions from the previous releasesoftware/ompi/nav.inc
and make this release series be the current stable release; shift other release series down as appropriatenightly/index.php
to make this release series be the current stable release; shift other release series snapshot tarballs down as appropriatesoftware/ompi/current/version.inc
to set the new release series as the current software release.software/ompi/major-changes.php
to list any incompatibilities from prior releases.version.inc
timeline-graph.php
(in the same directory asversion.inc
) to add a date stamp to the timeline graph for the release of this version (i.e., callmilestone()
like it is for the other releases)index.php
with a news bullet about this release. It is likely possible to guess the correct URL that will be used to web archive the announcement mail sent to announce@lists.open-mpi.orggit add doc/vRELEASE
doc/index.php
to list the new directory and git add itcurrent
sym link to point to the correct directory and git add itgit commit -s
to commit all the web site changesgit push
all web site changesopen-mpi/ompi
announce@lists.open-mpi.org
mailing list announcing the releaseannounce@open-mpi.org
) is correct on the front Open MPI web page.Prep for next release in series
VERSION
to<NEXT_VERSION>
and setgreek
toa1