Files
harbour-core/harbour/doc/howtorel.txt
Viktor Szakats a3f42e8991 2010-07-30 00:08 UTC+0200 Viktor Szakats (harbour.01 syenar.hu)
* debian/dirs
    ! Deleted doc/en dir.

  * doc/Makefile
  - doc/whatsnew.txt
  + NEWS
  * COPYING
  * doc/howtorel.txt
  * debian/changelog
  * package/mpkg_win.nsi
  * package/winuni/mpkg_win_uni.bat
  * package/winuni/mpkg_win_uni.nsi
    * Renamed doc/whatsnew.txt to /NEWS

  * debian/copyright
    * Updated with COPYING content.

  * package/harbour.spec
    ! Fixed to include doc/* instead of doc/*.txt.

  * utils/hbrun/hbrun.prg
    - Deleted envvar method of passing dirbase to scripts.

  * contrib/make.hbs
    + Using HBRUN_DIRBASE() function instead of envvar trick.
      Maybe some more generic named value passing would be better.

  * contrib/Makefile
    ! Using '-' prefix when running hbrun instead of '+', to not
      cause fatal breakage in build stage if make.hbs contains
      something which previous build of hbrun didn't offer.

  * config/global.mk
    - HB_INSTALL_PREFIX will not default anymore to source root
      dir (on non-*nix systems) to avoid FAQ where installation
      fails because of former install into source root, causing
      old contrib headers to ovveride current ones and breaking
      build. Please note that 'install' is truly optional with
      current builds, so only use it for what it was designed.
      Pls should if some things fail with empty HB_INSTALL_PREFIX
      and requesting 'install' anyway.

  * contrib/xhb/xhbat.c
    ! Applied this fix to Harbour:
      2010-07-29 12:28 UTC-0430 Ron Pinkas <ron.pinkas/at/xharbour.com>
        * source/rtl/at.c
          + Added missing extended strings support, to hb_AtSkipStrings()
2010-07-29 22:10:21 +00:00

43 lines
1.6 KiB
Plaintext

/*
* $Id$
*/
How to create and tag a new release
===================================
By Przemyslaw Czerpak (druzus/at/priv.onet.pl)
1. Make full update of your local CVS copy with:
cvs -z3 update -A -P -d -R harbour
with the above unused empty directories will be removed
from your repository copy.
Please check if all your files are unmodified. You can redirect
stdout output from cvs command to a file to see if all files are
exactly the same.
2. Update files which contain harbour release number. Now these are:
harbour.spec
include/hbver.h
3. Set proper release date in NEWS and if necessary update
release informations. Also add the exact tag name to this file,
for example "tag: build46".
4. Update ChangeLog file and commit your modifications.
5. Update hbver.h with ChangeLog file ID and your last entry ID.
6. Tag the CVS tree with the new release tag:
cvs tag -t -F -D <local_daytime_or_other_with_TZ_info> <newtag>
for example:
cvs tag -t -F -D "2006-05-29 16:00" build46
With the above you can also "re-tag" already set tag so be careful
and use re-tag repository _only_ if it's really necessary.
With properly tagged CVS any one who wants to create Harbour release
binaries should make:
cvs -z3 co -r <reltag> harbour
for example:
cvs -z3 co -r "build46" harbour
to be sure that local repository copy is exactly the same as the one
tagged as new release. The first commit after cvs tagging should also
change the version number and ChangeLog IDs in harbour.spec and
include/hbver.h for easier locating possible mistakes when release
binaries are created.