Difference: ReleaseProcedures (1 vs. 32)

Revision 322019-04-08 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Release procedures for frontier-related software

Line: 27 to 27
 
  1. If it is a new upstream squid version, do these steps
    SQUIDVER="`echo $FSQUIDVER|sed 's/-.*//'`"
    cd ~/src/frontier/tarballs/frontier-squid4/distrib
Added:
>
>
git rm squid-*.tar.gz*
 rm -rf squid-* wget http://www.squid-cache.org/Versions/v4/squid-$SQUIDVER.tar.gz wget http://www.squid-cache.org/Versions/v4/squid-$SQUIDVER.tar.gz.asc
Added:
>
>
git add squid-$SQUIDVER.tar.gz*
 gpg --verify squid-$SQUIDVER.tar.gz.asc squid-$SQUIDVER.tar.gz cd /tmp tar xzf $OLDPWD/squid-$SQUIDVER.tar.gz
Line: 52 to 54
 wget -qO- "https://gitlab.cern.ch/frontier/tarballs/frontier-squid4/repository/archive.tar.gz?ref=frontier-squid-$FSQUIDVER"|tar xzf - mv * frontier-squid-$FSQUIDVER tar cvf ../frontier-squid-$FSQUIDVER.tar.gz frontier-squid-$FSQUIDVER
Added:
>
>
cd .. rm -rf extract
 
  1. scp /tmp/frontier-squid-$FSQUIDVER.tar.gz dbfrontier@frontier.cern.ch:dist
  2. Update InstallSquidTarball twiki with new version

Revision 312019-04-03 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Release procedures for frontier-related software

Line: 26 to 26
 
  1. If it is a new upstream squid version, do these steps
    SQUIDVER="`echo $FSQUIDVER|sed 's/-.*//'`"
Changed:
<
<
cd ~/src/tarballs/frontier-squid4/trunk/distrib
>
>
cd ~/src/frontier/tarballs/frontier-squid4/distrib
 rm -rf squid-*
Changed:
<
<
wget http://www.squid-cache.org/Versions/v4/$SQUIDVER/squid-$SQUIDVER.tar.gz wget http://www.squid-cache.org/Versions/v4/$SQUIDVER/squid-$SQUIDVER.tar.gz.asc
>
>
wget http://www.squid-cache.org/Versions/v4/squid-$SQUIDVER.tar.gz wget http://www.squid-cache.org/Versions/v4/squid-$SQUIDVER.tar.gz.asc
 gpg --verify squid-$SQUIDVER.tar.gz.asc squid-$SQUIDVER.tar.gz cd /tmp tar xzf $OLDPWD/squid-$SQUIDVER.tar.gz cd squid-$SQUIDVER
Changed:
<
<
./configure --disable-wccp make
>
>
scl enable devtoolset-2 "./configure --disable-wccp" scl enable devtoolset-2 make
  Then compare /tmp/squid-$SQUIDVER/src/squid.conf.documented to squid/files/postinstall/squid.conf.documented and update it and the corresponding squid.conf.proto with the things that have changed (at minimum, the version number will always change).
  1. Add notes in the RELEASE_NOTES file for the new version.
Line: 65 to 65
 Frontier rpm releases have these steps in common (replace "package" with individual package name):
  1. If updating the tomcat version in frontier-tomcat, compare its conf/server.xml with src/conf/server.xml.O. If there are changes, update server.xml.O and server.xml.proto.
  2. Commit your changes to git.
Changed:
<
<
  1. Make sure you have created a working directory according to the instructions under "Building frontier rpms" step 1, a directory called "rpms" where each trunk for doc, scripts, and all frontier-* packages are checked out under their own name.
>
>
  1. Make sure you have created a working directory according to the instructions under "Building frontier rpms" step 1, a directory called "rpms" where each repository for doc, scripts, and all frontier-* packages are checked out under their own name.
 
  1. Update frontier-package/SPECS/frontier-package.spec with the new version, release4source, and releasenum, and commit to git.
  2. If the spec file has a %changelog, add a new entry and commit to git, otherwise edit frontier-package/doc/frontier-packageRELEASE_NOTES with the new version number and release notes, and commit that to git.
  3. Do git push to upload changes to the git server.

Revision 302019-04-01 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Release procedures for frontier-related software

Line: 65 to 65
 Frontier rpm releases have these steps in common (replace "package" with individual package name):
  1. If updating the tomcat version in frontier-tomcat, compare its conf/server.xml with src/conf/server.xml.O. If there are changes, update server.xml.O and server.xml.proto.
  2. Commit your changes to git.
Changed:
<
<
  1. Make sure you have created a working directory according to the instructions, a directory called "rpms" where each trunk for doc, scripts, and all frontier-* packages are checked out under their own name.
>
>
  1. Make sure you have created a working directory according to the instructions under "Building frontier rpms" step 1, a directory called "rpms" where each trunk for doc, scripts, and all frontier-* packages are checked out under their own name.
 
  1. Update frontier-package/SPECS/frontier-package.spec with the new version, release4source, and releasenum, and commit to git.
  2. If the spec file has a %changelog, add a new entry and commit to git, otherwise edit frontier-package/doc/frontier-packageRELEASE_NOTES with the new version number and release notes, and commit that to git.
  3. Do git push to upload changes to the git server.

Revision 292019-01-24 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Release procedures for frontier-related software

Line: 64 to 64
  Frontier rpm releases have these steps in common (replace "package" with individual package name):
  1. If updating the tomcat version in frontier-tomcat, compare its conf/server.xml with src/conf/server.xml.O. If there are changes, update server.xml.O and server.xml.proto.
Changed:
<
<
  1. Commit your changes to svn.
  2. Make sure you have created a working directory according to the instructions, a directory called "rpms" where each trunk for doc, scripts, and all frontier-* packages are checked out under their own name.
  3. Update frontier-package/SPECS/frontier-package.spec with the new version, release4source, and releasenum, and commit to svn.
  4. If the spec file has a %changelog, add a new entry and commit to svn, otherwise edit frontier-package/doc/frontier-packageRELEASE_NOTES with the new version number and release notes, and commit that to svn.
>
>
  1. Commit your changes to git.
  2. Make sure you have created a working directory according to the instructions, a directory called "rpms" where each trunk for doc, scripts, and all frontier-* packages are checked out under their own name.
  3. Update frontier-package/SPECS/frontier-package.spec with the new version, release4source, and releasenum, and commit to git.
  4. If the spec file has a %changelog, add a new entry and commit to git, otherwise edit frontier-package/doc/frontier-packageRELEASE_NOTES with the new version number and release notes, and commit that to git.
  5. Do git push to upload changes to the git server.
 
  1. In directory frontier-package/scripts on an SL6-based system, run ../../scripts/rpmbuild_.sh including entering your passphrase for the signature.
  2. In the same directory, run ../../scripts/rpm2web.sh /home/dbfrontier/dist/rpms-debug to publish the release to the cernvm-frontier-debug repo. You need to be on a machine on which you can do 'sudo -u dbfrontier' and which is set up with an ssh key to be able to scp from that account to dbfrontier@frontier.cern.ch.
  3. In the same directory, run ../../scripts/rpm2web.sh to install to the regular cernvm-frontier repo. Answer "yes" to the prompt.
Changed:
<
<
  1. In the same directory, run ../../scripts/svntag.sh to create the release tag in svn.
>
>
  1. In the same directory, run ../../scripts/gittag.sh to create the release tag.
 
  1. Send a release announcement to frontier-talk@cern.ch.

Revision 282019-01-24 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Release procedures for frontier-related software

Line: 22 to 22
 
  1. Update the SRC and RELEASE variables in squid/Makefile
  2. Set an environment variable for the new version, for example:
Changed:
<
<
FSQUIDVER=3.5.23-1
>
>
FSQUIDVER=4.4-1
 
  1. If it is a new upstream squid version, do these steps
    SQUIDVER="`echo $FSQUIDVER|sed 's/-.*//'`"
Changed:
<
<
cd ~/src/frontier/tarballs/frontier-squid3/trunk/distrib
>
>
cd ~/src/tarballs/frontier-squid4/trunk/distrib
 rm -rf squid-*
Changed:
<
<
wget http://www.squid-cache.org/Versions/v3/3.5/squid-$SQUIDVER.tar.gz wget http://www.squid-cache.org/Versions/v3/3.5/squid-$SQUIDVER.tar.gz.asc
>
>
wget http://www.squid-cache.org/Versions/v4/$SQUIDVER/squid-$SQUIDVER.tar.gz wget http://www.squid-cache.org/Versions/v4/$SQUIDVER/squid-$SQUIDVER.tar.gz.asc
 gpg --verify squid-$SQUIDVER.tar.gz.asc squid-$SQUIDVER.tar.gz cd /tmp tar xzf $OLDPWD/squid-$SQUIDVER.tar.gz
Line: 39 to 39
  Then compare /tmp/squid-$SQUIDVER/src/squid.conf.documented to squid/files/postinstall/squid.conf.documented and update it and the corresponding squid.conf.proto with the things that have changed (at minimum, the version number will always change).
  1. Add notes in the RELEASE_NOTES file for the new version.
Changed:
<
<
  1. Commit all changes into the frontier-squid svn trunk
  2. Create a new version tag for the new release, for example in your working node above the trunk:
    svn copy trunk tags/frontier-squid-$FSQUIDVER
    rm -rf tags/frontier-squid-$FSQUIDVER/distrib/squid-`echo $FSQUIDVER|sed 's/-.*//'`
    svn commit tags/frontier-squid-$FSQUIDVER -m 'Create tag'
>
>
  1. Commit all changes into git
  2. Create a new version tag for the new release and push to the repository, for example:
    git tag frontier-squid-$FSQUIDVER
    git push
    git push --tags
    
  3. scp RELEASE_NOTES dbfrontier@frontier.cern.ch:dist/frontier-squid-releasenotes.txt
  4. Create a tarball:
    mkdir /tmp/extract
    cd /tmp/extract
    wget -qO- "https://gitlab.cern.ch/frontier/tarballs/frontier-squid4/repository/archive.tar.gz?ref=frontier-squid-$FSQUIDVER"|tar xzf -
    mv * frontier-squid-$FSQUIDVER
    tar cvf ../frontier-squid-$FSQUIDVER.tar.gz frontier-squid-$FSQUIDVER
 
Deleted:
<
<
  1. scp trunk/RELEASE_NOTES dbfrontier@frontier.cern.ch:dist/frontier-squid-releasenotes.txt
  2. cd tags; tar czvf /tmp/frontier-squid-$FSQUIDVER.tar.gz --exclude .svn frontier-squid-$FSQUIDVER
 
  1. scp /tmp/frontier-squid-$FSQUIDVER.tar.gz dbfrontier@frontier.cern.ch:dist
  2. Update InstallSquidTarball twiki with new version

Revision 272018-08-28 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Release procedures for frontier-related software

Line: 45 to 45
 rm -rf tags/frontier-squid-$FSQUIDVER/distrib/squid-`echo $FSQUIDVER|sed 's/-.*//'` svn commit tags/frontier-squid-$FSQUIDVER -m 'Create tag'
Changed:
<
<
  1. scp -P 2222 trunk/RELEASE_NOTES dbfrontier@frontier.cern.ch:dist/frontier-squid-releasenotes.txt
>
>
  1. scp trunk/RELEASE_NOTES dbfrontier@frontier.cern.ch:dist/frontier-squid-releasenotes.txt
 
  1. cd tags; tar czvf /tmp/frontier-squid-$FSQUIDVER.tar.gz --exclude .svn frontier-squid-$FSQUIDVER
Changed:
<
<
  1. scp -P 2222 /tmp/frontier-squid-$FSQUIDVER.tar.gz dbfrontier@frontier.cern.ch:dist
>
>
  1. scp /tmp/frontier-squid-$FSQUIDVER.tar.gz dbfrontier@frontier.cern.ch:dist
 
  1. Update InstallSquidTarball twiki with new version

frontier-awstats tarball

Revision 262018-08-23 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Release procedures for frontier-related software

Line: 30 to 30
 rm -rf squid-* wget http://www.squid-cache.org/Versions/v3/3.5/squid-$SQUIDVER.tar.gz wget http://www.squid-cache.org/Versions/v3/3.5/squid-$SQUIDVER.tar.gz.asc
Added:
>
>
gpg --verify squid-$SQUIDVER.tar.gz.asc squid-$SQUIDVER.tar.gz
 cd /tmp tar xzf $OLDPWD/squid-$SQUIDVER.tar.gz cd squid-$SQUIDVER

Revision 252018-01-25 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Release procedures for frontier-related software

Line: 33 to 33
 cd /tmp tar xzf $OLDPWD/squid-$SQUIDVER.tar.gz cd squid-$SQUIDVER
Changed:
<
<
./configure
>
>
./configure --disable-wccp
 make Then compare /tmp/squid-$SQUIDVER/src/squid.conf.documented to squid/files/postinstall/squid.conf.documented and update it and the corresponding squid.conf.proto with the things that have changed (at minimum, the version number will always change).

Revision 242017-09-01 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Release procedures for frontier-related software

Line: 25 to 25
 FSQUIDVER=3.5.23-1
  1. If it is a new upstream squid version, do these steps
Deleted:
<
<
cd /tmp
 SQUIDVER="`echo $FSQUIDVER|sed 's/-.*//'`"
Changed:
<
<
tar xzf squid-$SQUIDVER.tar.gz
>
>
cd ~/src/frontier/tarballs/frontier-squid3/trunk/distrib rm -rf squid-* wget http://www.squid-cache.org/Versions/v3/3.5/squid-$SQUIDVER.tar.gz wget http://www.squid-cache.org/Versions/v3/3.5/squid-$SQUIDVER.tar.gz.asc cd /tmp tar xzf $OLDPWD/squid-$SQUIDVER.tar.gz
 cd squid-$SQUIDVER ./configure make

Revision 232017-03-27 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Release procedures for frontier-related software

Line: 53 to 53
  Frontier rpm releases have these steps in common (replace "package" with individual package name):
  1. If updating the tomcat version in frontier-tomcat, compare its conf/server.xml with src/conf/server.xml.O. If there are changes, update server.xml.O and server.xml.proto.
Changed:
<
<
  1. Commit your changes to svn
  2. Make sure you have created a working directory according to the instructions, a directory called "rpms" where each trunk for doc, scripts, and all frontier-* packages are checked out under their own name
  3. Update frontier-package/SPECS/frontier-package.spec with the new version, release4source, and releasenum, and commit to svn
>
>
  1. Commit your changes to svn.
  2. Make sure you have created a working directory according to the instructions, a directory called "rpms" where each trunk for doc, scripts, and all frontier-* packages are checked out under their own name.
  3. Update frontier-package/SPECS/frontier-package.spec with the new version, release4source, and releasenum, and commit to svn.
 
  1. If the spec file has a %changelog, add a new entry and commit to svn, otherwise edit frontier-package/doc/frontier-packageRELEASE_NOTES with the new version number and release notes, and commit that to svn.
Changed:
<
<
  1. In directory frontier-package/scripts on an SL6-based system, run ../../scripts/rpmbuild_.sh including entering your passphrase for the signature
  2. In the same directory, run ../../scripts/rpm2web.sh to publish the release. An optional parameter is another directory owned by dbfrontier on frontier.cern.ch to do a test install into, typically /home/dbfrontier/dist/rpms-debug. You need to be on a machine on which you can do 'sudo -u dbfrontier' and which is set up with an ssh key to be able to scp from that account to dbfrontier@frontier.cern.ch
  3. In the same directory, run ../../scripts/svntag.sh to create the release tag in svn
  4. Send a release announcement to frontier-talk@cern.ch
>
>
  1. In directory frontier-package/scripts on an SL6-based system, run ../../scripts/rpmbuild_.sh including entering your passphrase for the signature.
  2. In the same directory, run ../../scripts/rpm2web.sh /home/dbfrontier/dist/rpms-debug to publish the release to the cernvm-frontier-debug repo. You need to be on a machine on which you can do 'sudo -u dbfrontier' and which is set up with an ssh key to be able to scp from that account to dbfrontier@frontier.cern.ch.
  3. In the same directory, run ../../scripts/rpm2web.sh to install to the regular cernvm-frontier repo. Answer "yes" to the prompt.
  4. In the same directory, run ../../scripts/svntag.sh to create the release tag in svn.
  5. Send a release announcement to frontier-talk@cern.ch.

Revision 222016-12-19 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Release procedures for frontier-related software

Line: 22 to 22
 
  1. Update the SRC and RELEASE variables in squid/Makefile
  2. Set an environment variable for the new version, for example:
Changed:
<
<
FSQUIDVER=2.7.STABLE9-10
>
>
FSQUIDVER=3.5.23-1
 
  1. If it is a new upstream squid version, do these steps
    cd /tmp

Revision 212016-10-13 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Release procedures for frontier-related software

Line: 20 to 20
 

frontier-squid tarball

Changed:
<
<
  1. Update the RELEASE variable in squid/Makefile
>
>
  1. Update the SRC and RELEASE variables in squid/Makefile
 
  1. Set an environment variable for the new version, for example:
    FSQUIDVER=2.7.STABLE9-10
    

Revision 202016-10-10 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Release procedures for frontier-related software

Line: 52 to 52
 

RPMs

Frontier rpm releases have these steps in common (replace "package" with individual package name):

Added:
>
>
  1. If updating the tomcat version in frontier-tomcat, compare its conf/server.xml with src/conf/server.xml.O. If there are changes, update server.xml.O and server.xml.proto.
 
  1. Commit your changes to svn
  2. Make sure you have created a working directory according to the instructions, a directory called "rpms" where each trunk for doc, scripts, and all frontier-* packages are checked out under their own name
  3. Update frontier-package/SPECS/frontier-package.spec with the new version, release4source, and releasenum, and commit to svn

Revision 192016-09-13 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Release procedures for frontier-related software

Line: 37 to 37
 
  1. Commit all changes into the frontier-squid svn trunk
  2. Create a new version tag for the new release, for example in your working node above the trunk:
    svn copy trunk tags/frontier-squid-$FSQUIDVER
Changed:
<
<
rm -rf tags/distrib/squid-`echo $FSQUIDVER|sed 's/-.*//'`
>
>
rm -rf tags/frontier-squid-$FSQUIDVER/distrib/squid-`echo $FSQUIDVER|sed 's/-.*//'`
 svn commit tags/frontier-squid-$FSQUIDVER -m 'Create tag'
  1. scp -P 2222 trunk/RELEASE_NOTES dbfrontier@frontier.cern.ch:dist/frontier-squid-releasenotes.txt

Revision 182016-07-21 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Release procedures for frontier-related software

Line: 37 to 37
 
  1. Commit all changes into the frontier-squid svn trunk
  2. Create a new version tag for the new release, for example in your working node above the trunk:
    svn copy trunk tags/frontier-squid-$FSQUIDVER
Added:
>
>
rm -rf tags/distrib/squid-`echo $FSQUIDVER|sed 's/-.*//'`
 svn commit tags/frontier-squid-$FSQUIDVER -m 'Create tag'
  1. scp -P 2222 trunk/RELEASE_NOTES dbfrontier@frontier.cern.ch:dist/frontier-squid-releasenotes.txt

Revision 172016-07-14 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Release procedures for frontier-related software

Line: 32 to 32
 ./configure make
Changed:
<
<
Then compare /tmp/squid-$FSQUIDVER/src/squid.conf.documented to squid/files/postinstall/squid.conf.documented and update it and the corresponding squid.conf.proto with the things that have changed (at minimum, the version number will always change).
>
>
Then compare /tmp/squid-$SQUIDVER/src/squid.conf.documented to squid/files/postinstall/squid.conf.documented and update it and the corresponding squid.conf.proto with the things that have changed (at minimum, the version number will always change).
 
  1. Add notes in the RELEASE_NOTES file for the new version.
  2. Commit all changes into the frontier-squid svn trunk
  3. Create a new version tag for the new release, for example in your working node above the trunk:

Revision 162016-05-11 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Release procedures for frontier-related software

Line: 21 to 21
 

frontier-squid tarball

  1. Update the RELEASE variable in squid/Makefile
Changed:
<
<
  1. Add notes in the RELEASE_NOTES file for the new version.
  2. Commit all changes into the frontier-squid svn trunk
  3. Set an environment variable for the new version
>
>
  1. Set an environment variable for the new version, for example:
  FSQUIDVER=2.7.STABLE9-10
Added:
>
>
  1. If it is a new upstream squid version, do these steps
    cd /tmp
    SQUIDVER="`echo $FSQUIDVER|sed 's/-.*//'`"
    tar xzf squid-$SQUIDVER.tar.gz
    cd squid-$SQUIDVER
    ./configure
    make
    
    Then compare /tmp/squid-$FSQUIDVER/src/squid.conf.documented to squid/files/postinstall/squid.conf.documented and update it and the corresponding squid.conf.proto with the things that have changed (at minimum, the version number will always change).
  2. Add notes in the RELEASE_NOTES file for the new version.
  3. Commit all changes into the frontier-squid svn trunk
 
  1. Create a new version tag for the new release, for example in your working node above the trunk:
          svn copy trunk tags/frontier-squid-$FSQUIDVER
          svn commit tags/frontier-squid-$FSQUIDVER -m 'Create tag'

Revision 152016-03-28 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Release procedures for frontier-related software

Line: 23 to 23
 
  1. Update the RELEASE variable in squid/Makefile
  2. Add notes in the RELEASE_NOTES file for the new version.
  3. Commit all changes into the frontier-squid svn trunk
Added:
>
>
  1. Set an environment variable for the new version
          FSQUIDVER=2.7.STABLE9-10
    
 
  1. Create a new version tag for the new release, for example in your working node above the trunk:
Changed:
<
<
svn copy trunk tags/frontier-squid-2.7.STABLE9-10 svn commit tags/frontier-squid-2.7.STABLE9-10 -m 'Create tag'
>
>
svn copy trunk tags/frontier-squid-$FSQUIDVER svn commit tags/frontier-squid-$FSQUIDVER -m 'Create tag'
 
  1. scp -P 2222 trunk/RELEASE_NOTES dbfrontier@frontier.cern.ch:dist/frontier-squid-releasenotes.txt
Changed:
<
<
  1. cd tags; tar czvf /tmp/frontier-squid-2.7.STABLE9-10.tar.gz --exclude .svn frontier-squid-2.7.STABLE9-10
  2. scp -P 2222 /tmp/frontier-squid-2.7.STABLE9-10.tar.gz dbfrontier@frontier.cern.ch:dist
>
>
  1. cd tags; tar czvf /tmp/frontier-squid-$FSQUIDVER.tar.gz --exclude .svn frontier-squid-$FSQUIDVER
  2. scp -P 2222 /tmp/frontier-squid-$FSQUIDVER.tar.gz dbfrontier@frontier.cern.ch:dist
 
  1. Update InstallSquidTarball twiki with new version

frontier-awstats tarball

Line: 43 to 46
 
  1. Make sure you have created a working directory according to the instructions, a directory called "rpms" where each trunk for doc, scripts, and all frontier-* packages are checked out under their own name
  2. Update frontier-package/SPECS/frontier-package.spec with the new version, release4source, and releasenum, and commit to svn
  3. If the spec file has a %changelog, add a new entry and commit to svn, otherwise edit frontier-package/doc/frontier-packageRELEASE_NOTES with the new version number and release notes, and commit that to svn.
Changed:
<
<
  1. In directory frontier-package/scripts on an SL5-based system, run ../../scripts/rpmbuild_.sh including entering your passphrase for the signature
>
>
  1. In directory frontier-package/scripts on an SL6-based system, run ../../scripts/rpmbuild_.sh including entering your passphrase for the signature
 
  1. In the same directory, run ../../scripts/rpm2web.sh to publish the release. An optional parameter is another directory owned by dbfrontier on frontier.cern.ch to do a test install into, typically /home/dbfrontier/dist/rpms-debug. You need to be on a machine on which you can do 'sudo -u dbfrontier' and which is set up with an ssh key to be able to scp from that account to dbfrontier@frontier.cern.ch
  2. In the same directory, run ../../scripts/svntag.sh to create the release tag in svn
  3. Send a release announcement to frontier-talk@cern.ch
\ No newline at end of file

Revision 142014-12-22 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Release procedures for frontier-related software

Line: 42 to 42
 
  1. Commit your changes to svn
  2. Make sure you have created a working directory according to the instructions, a directory called "rpms" where each trunk for doc, scripts, and all frontier-* packages are checked out under their own name
  3. Update frontier-package/SPECS/frontier-package.spec with the new version, release4source, and releasenum, and commit to svn
Changed:
<
<
  1. Except for frontier-squid, edit frontier-package/doc/frontier-packageRELEASE_NOTES with the new version number and release notes, and commit to svn. In frontier-squid put them in the rpm %changelog section.
>
>
  1. If the spec file has a %changelog, add a new entry and commit to svn, otherwise edit frontier-package/doc/frontier-packageRELEASE_NOTES with the new version number and release notes, and commit that to svn.
 
  1. In directory frontier-package/scripts on an SL5-based system, run ../../scripts/rpmbuild_.sh including entering your passphrase for the signature
  2. In the same directory, run ../../scripts/rpm2web.sh to publish the release. An optional parameter is another directory owned by dbfrontier on frontier.cern.ch to do a test install into, typically /home/dbfrontier/dist/rpms-debug. You need to be on a machine on which you can do 'sudo -u dbfrontier' and which is set up with an ssh key to be able to scp from that account to dbfrontier@frontier.cern.ch
  3. In the same directory, run ../../scripts/svntag.sh to create the release tag in svn

Revision 132014-11-06 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Release procedures for frontier-related software

Line: 44 to 44
 
  1. Update frontier-package/SPECS/frontier-package.spec with the new version, release4source, and releasenum, and commit to svn
  2. Except for frontier-squid, edit frontier-package/doc/frontier-packageRELEASE_NOTES with the new version number and release notes, and commit to svn. In frontier-squid put them in the rpm %changelog section.
  3. In directory frontier-package/scripts on an SL5-based system, run ../../scripts/rpmbuild_.sh including entering your passphrase for the signature
Changed:
<
<
  1. In the same directory, run ../../scripts/rpm2web.sh to publish the release. An optional parameter is another directory owned by dbfrontier on frontier.cern.ch to do a test install into. You need to be on a machine on which you can do 'sudo -u dbfrontier' and which is set up with an ssh key to be able to scp from that account to dbfrontier@frontier.cern.ch
>
>
  1. In the same directory, run ../../scripts/rpm2web.sh to publish the release. An optional parameter is another directory owned by dbfrontier on frontier.cern.ch to do a test install into, typically /home/dbfrontier/dist/rpms-debug. You need to be on a machine on which you can do 'sudo -u dbfrontier' and which is set up with an ssh key to be able to scp from that account to dbfrontier@frontier.cern.ch
 
  1. In the same directory, run ../../scripts/svntag.sh to create the release tag in svn
  2. Send a release announcement to frontier-talk@cern.ch

Revision 122014-09-03 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Release procedures for frontier-related software

Line: 27 to 27
  svn copy trunk tags/frontier-squid-2.7.STABLE9-10 svn commit tags/frontier-squid-2.7.STABLE9-10 -m 'Create tag'
Changed:
<
<
  1. scp trunk/RELEASE_NOTES dbfrontier@frontier.cern.ch:dist/frontier-squid-releasenotes.txt
>
>
  1. scp -P 2222 trunk/RELEASE_NOTES dbfrontier@frontier.cern.ch:dist/frontier-squid-releasenotes.txt
 
  1. cd tags; tar czvf /tmp/frontier-squid-2.7.STABLE9-10.tar.gz --exclude .svn frontier-squid-2.7.STABLE9-10
Changed:
<
<
  1. scp /tmp/frontier-squid-2.7.STABLE9-10.tar.gz dbfrontier@frontier.cern.ch:dist
>
>
  1. scp -P 2222 /tmp/frontier-squid-2.7.STABLE9-10.tar.gz dbfrontier@frontier.cern.ch:dist
 
  1. Update InstallSquidTarball twiki with new version

frontier-awstats tarball

Revision 112013-05-09 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Release procedures for frontier-related software

Line: 41 to 41
 Frontier rpm releases have these steps in common (replace "package" with individual package name):
  1. Commit your changes to svn
  2. Make sure you have created a working directory according to the instructions, a directory called "rpms" where each trunk for doc, scripts, and all frontier-* packages are checked out under their own name
Changed:
<
<
  1. Update frontier-package/SPECS/frontier-package.spec with the new version number and commit to svn
>
>
  1. Update frontier-package/SPECS/frontier-package.spec with the new version, release4source, and releasenum, and commit to svn
 
  1. Except for frontier-squid, edit frontier-package/doc/frontier-packageRELEASE_NOTES with the new version number and release notes, and commit to svn. In frontier-squid put them in the rpm %changelog section.
Changed:
<
<
  1. In directory frontier-package/scripts, run ../../scripts/rpmbuild_.sh including entering your passphrase for the signature
>
>
  1. In directory frontier-package/scripts on an SL5-based system, run ../../scripts/rpmbuild_.sh including entering your passphrase for the signature
 
  1. In the same directory, run ../../scripts/rpm2web.sh to publish the release. An optional parameter is another directory owned by dbfrontier on frontier.cern.ch to do a test install into. You need to be on a machine on which you can do 'sudo -u dbfrontier' and which is set up with an ssh key to be able to scp from that account to dbfrontier@frontier.cern.ch
  2. In the same directory, run ../../scripts/svntag.sh to create the release tag in svn
  3. Send a release announcement to frontier-talk@cern.ch
\ No newline at end of file

Revision 102013-05-02 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Release procedures for frontier-related software

Line: 28 to 28
  svn commit tags/frontier-squid-2.7.STABLE9-10 -m 'Create tag'
  1. scp trunk/RELEASE_NOTES dbfrontier@frontier.cern.ch:dist/frontier-squid-releasenotes.txt
Changed:
<
<
  1. cd tags; tar czvf /tmp/frontier-squid-2.7.STABLE9-10.tar.gz frontier-squid-2.7.STABLE9-10
>
>
  1. cd tags; tar czvf /tmp/frontier-squid-2.7.STABLE9-10.tar.gz --exclude .svn frontier-squid-2.7.STABLE9-10
 
  1. scp /tmp/frontier-squid-2.7.STABLE9-10.tar.gz dbfrontier@frontier.cern.ch:dist
  2. Update InstallSquidTarball twiki with new version

Revision 92013-03-30 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Release procedures for frontier-related software

Line: 20 to 20
 

frontier-squid tarball

Changed:
<
<
  1. Commit all changes into the frontier-squid svn trunk, including a RELEASE_NOTES entry for the new version
>
>
  1. Update the RELEASE variable in squid/Makefile
  2. Add notes in the RELEASE_NOTES file for the new version.
  3. Commit all changes into the frontier-squid svn trunk
 
  1. Create a new version tag for the new release, for example in your working node above the trunk:
          svn copy trunk tags/frontier-squid-2.7.STABLE9-10
          svn commit tags/frontier-squid-2.7.STABLE9-10 -m 'Create tag'

Revision 82013-01-31 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Release procedures for frontier-related software

Line: 40 to 40
 
  1. Commit your changes to svn
  2. Make sure you have created a working directory according to the instructions, a directory called "rpms" where each trunk for doc, scripts, and all frontier-* packages are checked out under their own name
  3. Update frontier-package/SPECS/frontier-package.spec with the new version number and commit to svn
Changed:
<
<
  1. Edit frontier-package/doc/frontier-packageRELEASE_NOTES with the new version number and release notes, and commit to svn
>
>
  1. Except for frontier-squid, edit frontier-package/doc/frontier-packageRELEASE_NOTES with the new version number and release notes, and commit to svn. In frontier-squid put them in the rpm %changelog section.
 
  1. In directory frontier-package/scripts, run ../../scripts/rpmbuild_.sh including entering your passphrase for the signature
  2. In the same directory, run ../../scripts/rpm2web.sh to publish the release. An optional parameter is another directory owned by dbfrontier on frontier.cern.ch to do a test install into. You need to be on a machine on which you can do 'sudo -u dbfrontier' and which is set up with an ssh key to be able to scp from that account to dbfrontier@frontier.cern.ch
  3. In the same directory, run ../../scripts/svntag.sh to create the release tag in svn

Revision 72013-01-17 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Release procedures for frontier-related software

Line: 39 to 39
 Frontier rpm releases have these steps in common (replace "package" with individual package name):
  1. Commit your changes to svn
  2. Make sure you have created a working directory according to the instructions, a directory called "rpms" where each trunk for doc, scripts, and all frontier-* packages are checked out under their own name
Deleted:
<
<
  1. update frontier-package/SPECS/frontier-package.spec with the new version number and commit to svn
  2. edit frontier-package/doc/frontier-packageRELEASE_NOTES with the new version number and release notes, and commit to svn
  3. in directory frontier-package/scripts, run ../../scripts/rpmbuild_.sh including entering your passphrase for the signature
  4. in the same directory, run ../../scripts/rpm2web.sh to publish the release. An optional parameter is another directory owned by dbfrontier on frontier.cern.ch to do a test install into. You need to be on a machine on which you can do 'sudo -u dbfrontier' and which is set up with an ssh key to be able to scp from that account to dbfrontier@frontier.cern.ch
  5. in the same directory, run ../../scripts/svntag.sh to create the release tag in svn
 \ No newline at end of file
Added:
>
>
  1. Update frontier-package/SPECS/frontier-package.spec with the new version number and commit to svn
  2. Edit frontier-package/doc/frontier-packageRELEASE_NOTES with the new version number and release notes, and commit to svn
  3. In directory frontier-package/scripts, run ../../scripts/rpmbuild_.sh including entering your passphrase for the signature
  4. In the same directory, run ../../scripts/rpm2web.sh to publish the release. An optional parameter is another directory owned by dbfrontier on frontier.cern.ch to do a test install into. You need to be on a machine on which you can do 'sudo -u dbfrontier' and which is set up with an ssh key to be able to scp from that account to dbfrontier@frontier.cern.ch
  5. In the same directory, run ../../scripts/svntag.sh to create the release tag in svn
  6. Send a release announcement to frontier-talk@cern.ch
 \ No newline at end of file

Revision 62013-01-11 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Release procedures for frontier-related software

Line: 40 to 40
 
  1. Commit your changes to svn
  2. Make sure you have created a working directory according to the instructions, a directory called "rpms" where each trunk for doc, scripts, and all frontier-* packages are checked out under their own name
  3. update frontier-package/SPECS/frontier-package.spec with the new version number and commit to svn
Changed:
<
<
  1. edit frontier-package/docs/frontier-packageRELEASE_NOTES with the new version number and release notes, and commit to svn
>
>
  1. edit frontier-package/doc/frontier-packageRELEASE_NOTES with the new version number and release notes, and commit to svn
 
  1. in directory frontier-package/scripts, run ../../scripts/rpmbuild_.sh including entering your passphrase for the signature
  2. in the same directory, run ../../scripts/rpm2web.sh to publish the release. An optional parameter is another directory owned by dbfrontier on frontier.cern.ch to do a test install into. You need to be on a machine on which you can do 'sudo -u dbfrontier' and which is set up with an ssh key to be able to scp from that account to dbfrontier@frontier.cern.ch
  3. in the same directory, run ../../scripts/svntag.sh to create the release tag in svn
\ No newline at end of file

Revision 52012-12-26 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Release procedures for frontier-related software

Line: 39 to 39
 Frontier rpm releases have these steps in common (replace "package" with individual package name):
  1. Commit your changes to svn
  2. Make sure you have created a working directory according to the instructions, a directory called "rpms" where each trunk for doc, scripts, and all frontier-* packages are checked out under their own name
Changed:
<
<
  1. update frontier-package/SPECS/frontier-package.spec with the new version number and commit
  2. edit frontier-package/docs/frontier-packageRELEASE_NOTES with the new version number and release notes
>
>
  1. update frontier-package/SPECS/frontier-package.spec with the new version number and commit to svn
  2. edit frontier-package/docs/frontier-packageRELEASE_NOTES with the new version number and release notes, and commit to svn
 
  1. in directory frontier-package/scripts, run ../../scripts/rpmbuild_.sh including entering your passphrase for the signature
Changed:
<
<
  1. in the same directory, run ../../scripts/rpm2web.sh. An optional parameter is another directory owned by dbfrontier on frontier.cern.ch to do a test install into. You need to be on a machine on which you can do 'sudo -u dbfrontier' and which is set up with an ssh key to be able to scp from that account to dbfrontier@frontier.cern.ch
>
>
  1. in the same directory, run ../../scripts/rpm2web.sh to publish the release. An optional parameter is another directory owned by dbfrontier on frontier.cern.ch to do a test install into. You need to be on a machine on which you can do 'sudo -u dbfrontier' and which is set up with an ssh key to be able to scp from that account to dbfrontier@frontier.cern.ch
 
  1. in the same directory, run ../../scripts/svntag.sh to create the release tag in svn

Revision 42012-12-21 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Release procedures for frontier-related software

Line: 36 to 36
 

RPMs

Changed:
<
<
Rpm releases have these steps in common (replace "package" with individual package name):
  1. Commit everything to svn
  2. Assuming you have created a working directory according to the instructions, where each trunk for doc, scripts, and all frontier-* packages are checked out under their own name, update frontier-package/SPECS/frontier-package.spec with the new version number and commit
>
>
Frontier rpm releases have these steps in common (replace "package" with individual package name):
  1. Commit your changes to svn
  2. Make sure you have created a working directory according to the instructions, a directory called "rpms" where each trunk for doc, scripts, and all frontier-* packages are checked out under their own name
  3. update frontier-package/SPECS/frontier-package.spec with the new version number and commit
 
  1. edit frontier-package/docs/frontier-packageRELEASE_NOTES with the new version number and release notes
  2. in directory frontier-package/scripts, run ../../scripts/rpmbuild_.sh including entering your passphrase for the signature
Deleted:
<
<
  1. in the same directory, run ../../scripts/rpm2web.sh. An optional parameter is another directory owned by dbfrontier on frontier.cern.ch to do a test install into.
  2. TO DO: add instruction for making tag

frontier-release rpm

frontier-squid rpm

frontier-tomcat rpm

frontier-awstats rpm

 \ No newline at end of file
Added:
>
>
  1. in the same directory, run ../../scripts/rpm2web.sh. An optional parameter is another directory owned by dbfrontier on frontier.cern.ch to do a test install into. You need to be on a machine on which you can do 'sudo -u dbfrontier' and which is set up with an ssh key to be able to scp from that account to dbfrontier@frontier.cern.ch
  2. in the same directory, run ../../scripts/svntag.sh to create the release tag in svn

Revision 32012-12-20 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Release procedures for frontier-related software

Line: 20 to 20
 

frontier-squid tarball

Changed:
<
<
  1. Check in and commit all changes into the frontier-squid svn trunk, including a RELEASE_NOTES entry for the new version
>
>
  1. Commit all changes into the frontier-squid svn trunk, including a RELEASE_NOTES entry for the new version
 
  1. Create a new version tag for the new release, for example in your working node above the trunk:
          svn copy trunk tags/frontier-squid-2.7.STABLE9-10
          svn commit tags/frontier-squid-2.7.STABLE9-10 -m 'Create tag'
Line: 32 to 32
 

frontier-awstats tarball

Added:
>
>
Basically similar to the frontier-squid tarball except without the copy of the release notes or twiki update. The only user is the rpm.
 

RPMs

Added:
>
>
Rpm releases have these steps in common (replace "package" with individual package name):
  1. Commit everything to svn
  2. Assuming you have created a working directory according to the instructions, where each trunk for doc, scripts, and all frontier-* packages are checked out under their own name, update frontier-package/SPECS/frontier-package.spec with the new version number and commit
  3. edit frontier-package/docs/frontier-packageRELEASE_NOTES with the new version number and release notes
  4. in directory frontier-package/scripts, run ../../scripts/rpmbuild_.sh including entering your passphrase for the signature
  5. in the same directory, run ../../scripts/rpm2web.sh. An optional parameter is another directory owned by dbfrontier on frontier.cern.ch to do a test install into.
  6. TO DO: add instruction for making tag
 

frontier-release rpm

Revision 22012-12-20 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Release procedures for frontier-related software

Line: 18 to 18
 

Tarballs

Changed:
<
<

frontier-squid

>
>

frontier-squid tarball

 
Changed:
<
<

frontier-awstats

>
>
  1. Check in and commit all changes into the frontier-squid svn trunk, including a RELEASE_NOTES entry for the new version
  2. Create a new version tag for the new release, for example in your working node above the trunk:
          svn copy trunk tags/frontier-squid-2.7.STABLE9-10
          svn commit tags/frontier-squid-2.7.STABLE9-10 -m 'Create tag'
    
  3. scp trunk/RELEASE_NOTES dbfrontier@frontier.cern.ch:dist/frontier-squid-releasenotes.txt
  4. cd tags; tar czvf /tmp/frontier-squid-2.7.STABLE9-10.tar.gz frontier-squid-2.7.STABLE9-10
  5. scp /tmp/frontier-squid-2.7.STABLE9-10.tar.gz dbfrontier@frontier.cern.ch:dist
  6. Update InstallSquidTarball twiki with new version

frontier-awstats tarball

 

RPMs

Changed:
<
<

frontier-squid

>
>

frontier-release rpm

 
Changed:
<
<

frontier-tomcat

>
>

frontier-squid rpm

 
Changed:
<
<

frontier-awstats

>
>

frontier-tomcat rpm

 
Deleted:
<
<

frontier-release

 \ No newline at end of file
Added:
>
>

frontier-awstats rpm

Revision 12012-12-20 - DaveDykstra

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="WebHome"

Release procedures for frontier-related software

The Frontier system has many releasable pieces to it, and here are the procedures for each piece for developers to use.

This is what is on this page:

Client

To be moved here, but for now at http://frontier.cern.ch/dist/FrontierProjectNotes.html

Servlet

To be moved here, but for now at http://frontier.cern.ch/dist/FrontierProjectNotes.html

Tarballs

frontier-squid

frontier-awstats

RPMs

frontier-squid

frontier-tomcat

frontier-awstats

frontier-release

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback