John Poelstra
poelstra@redhat.com
2010-10-27

You must follow the same naming conventions for the file names and directories for everything to work with the Red Hat Product pages, etc.

This file should be updated at the beginning of each Fedora release to reflect the current steps for build the next release's schedule

For this example we're assuming that Fedora 15 is the new release and Fedora 14 is the previous release and that you've never setup or used CVS before.

1) Setup a simple aliases to set enviornmental variables for Red Hat's CVS
   alias envecs='export CVS_RSH=ssh; export CVSROOT=cvs.devel.redhat.com:/cvs/ecs'
   alias cvsecs='cvs -d :ext:your-kerberos-user-name@cvs.devel.redhat.com:/cvs/ecs'

2) Change to directory that is suitable for saving internal-only Red Hat information and set enviornment variables (e.g. encrypted home directory)
   $ cd my-encrypted-home-dir
   $ envecs

3) Check out from internal CVS for the first time -OR- 
   $ cvsecs co program
    
   OR refresh current checkout
   
   $ cvsecs up -dP

4) Change to your local 'program/fedora' directory
  $ cd program/fedora

5) Make a new directory for the new release
  $ mkdir f-15  (you must follow this naming convention)

6) Commit the new directory to CVS
  $ addcvs f-15

7) Copy the files from the previous release to the new folder, changing the names as appropriate. Roll the schedules files from the previous release to the new directory.  We will use these as a starting place for the new release.  IMPORTANT: rename f-14.tjp to f-15.tjp
  $ cd program/fedora/f-14 
  $ cp f-14.tjp ../f-15/f-15.tjp 
  $ cp combine-art-releng.xsl \
       combine-docs-releng.xsl \
       combine-docs-translation.xsl \
       format-weekly-calendar.py \
       Makefile \
       Makefile.custom \
       reports.tji  \
       self-hosting.readme \
       new-schedule.README-INTERNAL \ 
       ../f-15

8) cd ../fedora/f-15

8) Modify the Makefile to reflect the correct values:
  MAJOR
  PRIOR_RELEASE

9) Edit the f-15.tjp file into shape
  a) update the comments and macros at the start of the file
  b) remove all "actual" task lengths
  c) Follow other prescribed steps in f-15.tjp

10) Edit self-hosting.readme to reflect the new version and relevant information

11) Add the new files to CVS
  $ cd f-15
  $ cvs add *

12) Commit the files
  $ cvs ci -m "your commit message"

13) Once you are statisfied that you have an acceptable draft schedule update the master makefile so that the new release schedule is built internally.  This is important for the Product Pages to pick up your compiled schedules.
   add f-15 to program/Makefile

14) Commit program/Makefile to cvs

15) Create a '.cvsignore' file
   a) $ make (generates schedule files)
   b) copy/paste report files with "?" in front of them and add them to a file called .cvsignore
   c) $ cvs add .cvsignore
   d) $ cvs ci .cvsignore