-
Notifications
You must be signed in to change notification settings - Fork 178
Release Version
Making a new release requires administrator permission.
To make a release of the Modelica library, proceed as follows:
-
Address all milestones for this release, https://github.com/lbl-srg/modelica-buildings/milestones
-
Merge all changes to the
release,maint_*ormasterbranch. -
Make sure the regression tests for
Buildings.Templateshave been run (as they use a checksum ofBuildings.Templatesonly and are not automatically triggered if other models change). -
Update the first lines in the file
Buildings/package.mo, such asannotation ( version="1.0.0", versionDate="2011-11-04", dateModified = "2011-12-08", uses(Modelica(version="3.2")), conversion( from(version="0.12", script="modelica://Buildings/Resources/Scripts/Dymola/ConvertModelica_from_0.12.0_to_0.13.mos")),
We use semantic versioning as described at http://semver.org/. Hence, major version X (X.y.z | X > 0) must be incremented if any backwards incompatible changes are introduced to the public API
The keyword
versionDateis only changed when the second digit ofversionchanges. The keyworddateModifiedis changed with each new patch. Use the date format above, which can be processed by Modelica tools. -
On the branch that has the files to be released, change
README.mdto update the lineDownload [Buildings Library 1.4.1 (2013-01-31)](https://github.com/lbl-srg/modelica-buildings/archive/v1.4.1.zip)
For release candidate 1 of version 2.0.0, use
Download [Buildings Library 2.0.0-rc.1 (2015-04-09)](https://github.com/lbl-srg/modelica-buildings/archive/v2.0.0-rc.1.zip)
-
Make sure that the conversion script, such as
ConvertBuildings_from_1.6_to_2.0.mos, contains all update commands. -
Update the user guide by typing
cd Buildings/Resources/Documentation/userGuide make html make linkcheck make copytowww -
Run the script
make_release.pywith arguments such asmake_release.py --version 1.0.0 --base-branch master
or
make_release.py --version 1.0.0-rc.1 --base-branch master
-
On https://github.com/lbl-srg/modelica-buildings/releases,
- make sure the release notes and the release asset, such as
Buildings-v8.0.0.zipare uploaded to the release page. This zip file contains all binaries. - enable discussions under "announcements".
- make sure the release notes and the release asset, such as
-
Copy the files to the web server using the script
postBuildingsTagToSrg.sh
(This step will start Dymola to export the html documentation, and also clean up the formatting of the documentation.)
-
Update http://simulationresearch.lbl.gov/modelica/download.html
- Add to list of releases.
- Add blog post.
-
Update the web link using
cd /usr/local/www/simulationresearch/modelica/releases rm latest && ln -s vX.Y.Z latest
-
Prepare next development version by:
-
Adding a new
ReleaseNotespackage toBuildings/package.mo. Use this template. -
Update in
Buildings/package.mothe sectionannotation ( version="1.1.1", versionDate="2011-11-04", dateModified="2011-12-07", uses(Modelica(version="3.2")),
-
Update in the same file
annotation (Documentation(info="<html> <p> This section summarizes the changes that have been performed on the Buildings library. </p> <p> <ul> <li> <a href="modelica://Buildings.UsersGuide.ReleaseNotes.Version_1_4_1"> Version 1.4.1</a>(xxx, 2013) </li> </li>
To update only the user guide, proceed as follows:
-
Type
git checkout master git pull cd Buildings/Resources/Documentation/userGuide -
Either type
make dist
or
make html make linkcheck make copytowww
The second form can be used if
make linkcheckreports broken links because links point to http://simulationresearch.lbl.gov/modelica/releases/latest/help/Buildings.html and hence files that were added to the current release may not yet be posted underlatest.