New BRAT revision - again!

From: Christian Holm Christensen (cholm@hehi03.nbi.dk)
Date: Wed Jul 18 2001 - 06:56:13 EDT

  • Next message: Flemming Videbaek: "Brat update (from Djamel)"

    Hi All, 
    
    I've tagged BRAT - again! - since there was a problem with the
    previous tag - again! 
    
      Version: 2.0.10 
      CVS tag: BRAT-2-0-10 
    
    The problem was, that someone (they know who they are) forgot to
    commit some file (they know which ones) _before_ tagging BRAT. 
    
    I've also update the AFS binary installation in new. 
    
    Ok, to make things absolutly clear as the day, here's what you should
    do when making a new revision: 
    
    1) Make your changes. 
    
    2) Clean your source tree: 
    
         make clean 
    
    3) Check that no-one has made any changes in between your last update
       and now: 
    
         cvs update -A -P -d 
    
    4) If any lines in the output from 3 started with 'C', resolve the
       conflicts in those files, and go back to 1
    
    3) Try to compile BRAT 
    
         make install 
    
    4) If the above fails go back to 1. 
    
    5) Run some tests of BRAT. I this fails, go back to 1
    
    6) If BRAT build and installed without problems, update the
       configure.in file. You should edit the line 
    
         AM_INIT_AUTOMAKE(brat, <version>)          
    
       So that <version> is the new version you want to make (e.g.,
       2.0.11) 
    
    7) Check in all your changes.  To see which files you've modified,
       added or removed, do 
    
         cvs -n update 
    
       Any file where the line starts with 'R', 'A', 'M' you need to
       commit. 
    
         cvs commit <removed/added/modified file> 
    
    8) Now tag the CVS repsitory 
    
         cvs tag BRAT-<cvs-like version> 
    
       where <cvs-like version> is <major>-<minor>-<revision> 
    
    9) Send an email to brahms-soft-l stating _all_ your changes.  I like
       to use the Emacs generated ChangeLog file (C-x v g), since that will
       extract all the CVS log messages.  In that way, I can also document
       changes that are sent to brahms-dev-l or brahms-soft-l - ofcourse
       that should never happen, but some people (they know who they are)
       are very VERY bad at communicating thier changes to thier fellow
       collaborators (shame on them). 
    
    The reason why it's soooo SOOO important to follow this procedure, is
    that otherwise it's a pain in the arse to maintain the binary
    installations, impossible to keep up with the changes and generally
    bad behaviour. 
    
    I'll update the BRAT Guide soon to reflect the changes in BRAT 2. 
    
    Yours, 
    
    Christian  -----------------------------------------------------------
    Holm Christensen                             Phone:  (+45) 35 35 96 91 
      Sankt Hansgade 23, 1. th.                  Office: (+45) 353  25 305 
      DK-2200 Copenhagen N                       Web:    www.nbi.dk/~cholm    
      Denmark                                    Email:       cholm@nbi.dk
    



    This archive was generated by hypermail 2b30 : Wed Jul 18 2001 - 06:56:33 EDT