PrepareRelease: Difference between revisions

From Openrtk
Jump to navigation Jump to search
No edit summary
Line 40: Line 40:
== Prepare binaries ==
== Prepare binaries ==


=== Linux ===
Binaries will now be posted by CI, simply verify that the Github action goes well and that the packages have been posted once it's over.
 
* Check that the docker service is running (<code>sudo service docker status</code>) and restart it if not (<code>sudo service docker restart</code>).
* Go to a directory, e.g. <code>mkdir ~/RTKpkg; cd ~/RTKpkg</code>.
* Clone RTK <code>git clone https://github.com/SimonRit/RTK.git</code>.
* Launch <code>RTKPythonPackage/BuildLinuxWheels.sh</code>.
 
=== Windows ===
 
* In <code>C:\P</code>,clone RTK <code>git clone https://github.com/SimonRit/RTK.git</code>.
* In <code>C:\P</code>,clone ITKPythonPackage <code>git clone https://github.com/InsightSoftwareConsortium/ITKPythonPackage IPP</code>.
* In Windows PowerShell, launch <code>./BuildWindowsWheels.ps1</code>.

Revision as of 08:43, 27 January 2021


Check ITK's instructions and update this wiki page accordingly.

Prepare release message

Based on the previous ones, e.g., the ones of v1.3, v1.4 and v2.0.

git log --no-merges v2.0.0..HEAD --pretty=format:"%h; %an; %ad: %s" >release_notes.txt
git log --no-merges v2.0.0..HEAD --pretty=format:"%an" | sort -u >contributors.txt

Prepare repository

Modify release number in CMakeLists.txt and setup.py. Modify required version for python packages in setup.py.

Tag git repository on this change with a copy of the release message.

Backup Doxygen documentation

ctest -S /home/srit/src/rtk/rtk-dashboard/russula_doxygen.cmake -V
cd /home/srit/src/rtk/RTK-website/
mv  /home/srit/src/rtk/dashboard_tests/RTK-Doxygen/Doxygen/html Doxygen140
./sync.sh

Prepare website

Create news message in RTK/news, update rtkindex.html and RTK/news/lefthand.html accordingly.

Update page RTK/resources/software.html.

Announce

Post message on the mailing list rtk-users@openrtk.org.

Prepare binaries

Binaries will now be posted by CI, simply verify that the Github action goes well and that the packages have been posted once it's over.