Skip to content

Latest commit

 

History

History
115 lines (75 loc) · 4.22 KB

70_release.md

File metadata and controls

115 lines (75 loc) · 4.22 KB
Raw

Make a new release

Making a new release involves the following steps:

  1. Update the release.notes
  2. make a release branch
  3. fix the versions in requirements.txt and commit it in the branch
  4. build DIRACOS
  5. deploy the archive

First of all, get the latest master branch, from which we perform the release. Careful, you are working with the main repository !

   git clone [email protected]:DIRACGrid/DIRACOS.git
   cd DIRACOS

Updating the release.notes

This has to be done using this script in the DIRAC repository:

Documentation on how to use it can be found here

Once the release.notes is updated, commit and push to the master branch.

   git add release.notes
   git commit -m "release.notes update for version XYZ"
   git push origin master

Make a release branch

   # Start a new branch
   # Note we wont push the branch, just the tag
   git checkout -b branch_XYZ

Fix the pip requirements versions

The aim of this step is to have a requirements.txt with fixed version for every package, such that it is fixed in time. You can of course do it manually... Otherwise, there is a utility script dos-fix-pip-versions. This script will start from a requirements.txt file with loose versions, and do the following:

  • packages from git are left untouched
  • requirements == are left untouched
  • requirements <= are fixed to ==
  • requirements >= are fixed to the latest version available
  • requirements with no version are fixed to the latest available

For packages taken from git, you will have to fix the version yourself by hand (see bellow).

The requirements.txt file in the master branch is (and should remain!) with loose version. The script will start from the pipRequirements file in the configuration, and produce an output file. You should then take this output file, fix the git version, and put it in your new branch.

This script requires the same setup as a build of DIRACOS. Thus, you can already setup you environment just like if you were about to build DIRACOS (see instructions). Once your environment is ready:

   [root@c4e49b1711e6 config]# dos-fix-pip-versions /tmp/DIRACOS/config/diracos.json
   [...]
   Fixing the version
   Finish: shell
   Fixed version file in /var/lib/mock/epel-6-x86_64-install/root/tmp/fixed_requirements.txt

You can then get the output file (/var/lib/mock/epel-6-x86_64-install/root/tmp/fixed_requirements.txt) and put it in replacement of the existing requirements.txt, after inspecting it.

NOTE: You have to execute dos-fix-pip-versions after you executed dos-build-all-rpms and you need to copy fixed_requirements.txt out of /var/lib/mock/epel-6-x86_64-install/root/tmp/ before proceeding with the execution of any other command as it might delete fixed_requirements.txt.

Once you are satisfied, you can update the version in the json file, commit, tag and push the branch

   # Update the version in the json file
   vim config/diracos.json
   # Note: do not use emacs, it would screw it all up...

   # Commit the changes in the requirements.txt and diracos.json
   git add config
   git commit -m "Fix versions in requirements.txt for version XYZ"
   # Make the release tag
   git tag -a XYZ -m "XYZ"
   # push it all
   git push --tags origin XYZ

About git packages

At the moment, there are only two packages taken from git:

  • fts-rest: only stable versions are tagged, so just use the latest one.
  • pyGSI: same applies, use the latest tag

Reminder: to install from a given branch: git+https://:@gitlab.cern.ch:8443/fts/fts-rest.git@myBranch#egg=fts3 (the egg parameter is the name that the package will take)

Build DIRACOS

All here.

Just make sure to use the tag you just created

Deploy the archive

The archive should be placed in /eos/project/d/diracos/www/releases

Generate the signature of the archive

   md5sum diracos-1.1.1.tar.gz | awk {'print $1'} > diracos-1.1.1.md5

Copy the tarball and the md5 file in the release directory