OCL/Dev/Releng/Quiet Week

In this wiki entry we explain the releng bits that may be done during the quiet week, particularly to the Eclipse OCL project. You may find some general information about the quite week in the Simultaneous Release Final Daze documentation (Juno, for the time of writing).

The following are the Eclipse OCL usal releng tasks to be accomplished during the quite week.

Hide the new release in the downloads web page

Prior to prepare the downloadable zips of the imminent release in the downloads area, we should ensure that they are not available for downloading. To do that you must follow the following steps:

• Clone the OCL www repository using the following GIT repository URL: ssh://git.eclipse.org/gitroot/www.eclipse.org/modeling/mdt.git
• Import the mdt project into the workspace
• Edit the /mdt/downloads/hidden.txt file and include an entry for the new release to hide, for instance modeling/mdt/4.0.2/R201301281158

   note: see the hidden.txt file history to find examples of previous modifications

• Commit and push the change to the remote repository

Prepare the downoadable zips area

We usually will want our last published RC to be our final version of the release which will be present in the downloads area. To do that we will have to follow the following stetps:

• Copy the last RC (Sxxxxxxxxxxxx for SR0 or Mxxxxxxxxxxxx for SR1 and SR0) taking into account that a release distribution should start with R. For instance, for the Juno SR2 release you should do the following:

~/downloads/modeling/mdt/ocl/downloads/drops/4.0.0> cp -rf M201301281158/ ../4.0.2/R201301281158

• Giving that the zips usually have the RCx suffix of the last Release Candidate built. We need to manually remove them. The following bash script does it automatically:

#!/bin/bash
# Copyright (c) 2013 Willink Transformations, University of York and others.
# All rights reserved. This program and the accompanying materials
# are made available under the terms of the Eclipse Public License v1.0
# which accompanies this distribution, and is available at
# http://www.eclipse.org/legal/epl-v10.html
#
# Contributors:
#               Adolfo Sanchez-Barbudo Herrera (Univerisity of York) - Initial API and implementation
if [ $# -ne 1 ]
then
   echo "usage example: ./renameZips.sh RC1"
   exit;
fi

for i in *.zip
do
  newName=${i/$1/}
  echo "Renaming $i to $newName"
  mv "$i" "$newName"
done

• Similarly, the md5 files need to be changed:

#!/bin/bash
# Copyright (c) 2013 Willink Transformations, University of York and others.
# All rights reserved. This program and the accompanying materials
# are made available under the terms of the Eclipse Public License v1.0
# which accompanies this distribution, and is available at
# http://www.eclipse.org/legal/epl-v10.html
#
# Contributors:
#               Adolfo Sanchez-Barbudo Herrera (Univerisity of York) - Initial API and implementation
if [ $# -ne 1 ]
then
   echo "usage example: ./renameMD5.sh RC1"
   exit;
fi

for i in *.md5
do
  iContent=`cat $i`
  newName=${i/$1/}
  newContent=${iContent/$1/}
  echo "Introducing $newContent into $newName"
  echo "$newContent" > "$newName"
  rm $i
done

• Finally, a small script to verify the MD5 checksum

#!/bin/bash
# Copyright (c) 2013 Willink Transformations, University of York and others.
# All rights reserved. This program and the accompanying materials
# are made available under the terms of the Eclipse Public License v1.0
# which accompanies this distribution, and is available at
# http://www.eclipse.org/legal/epl-v10.html
#
# Contributors:
#               Adolfo Sanchez-Barbudo Herrera (Univerisity of York) - Initial API and implementation
for i in *.md5
do
  md5sum -c $i
done