FreeTDS Development Group

["James K. Lowden" <jklowden AT freetds.org>]

On Sat, 10 Mar 2012 17:56:15 -0500
"James K. Lowden" <jklowden AT freetds.org> wrote:

> what is the best way to get the latest HEAD and branch code?  

Thanks to you both.  Tell me if this is sane.  

1.  I ran "git clone" to create a local repository.  
2.  Each night, I'll run 
 2a.    "git pull" to update the local repository
 2b.    For each branch (currently "master" and "Branch-0.91")
  2b1   git clean
  2b2   git checkout $BRANCH
  2b3   next branch if revision number unchanged
  2b4   autoconf etc. to make tarball publish publish

To test the revision number, I use  

oak[freetds.git]$ for BRANCH in master Branch-0_91 
 do 
        git show-branch \
        | awk -F '[][~]' "/${BRANCH}/ { print \$3,\$2 }" \
        | sort -rn | head -1
 done 

yielding: 

        275 master 
        46 Branch-0_91

The version numbers then become:

        freetds-0.92.dev.275
        freetds-0.91.46

SONAMEs and tarball names will be similar.  

Anyone wanting to know the date can consult the repository or look at
the top of ChangeLog.  (Some documentation would doubtless help.)  

The monotonically incrementing version number is more informative than
the date:  If you hold version X and see current is version Y, 
then Y - X tells you how many commits transpired meanwhile.  That's more
important than the date the version was produced.  

For the purpose of generating the tarball ISTM I don't need a separate
working directory.  (I might for day-to-day use; like Frediano, I also
don't want to lose files I haven't checked in.)  The tarball is
generated; the next day any unversioned/modified files are purged by
"git clean".  

This process is significantly simpler than the one I use today.
Because CVS has nothing like a repository version number, I needed to
keep "yesterday's" MD5 (of the whole tree) to compare with today's
checkout.  

Expect to see git-produced tarballs tonight.  

        Issues
        ------

0.  Any concerns, questions, or suggestions with the above.  

1.  Signore Ziglio, prego, could I have commit rights to the
repository? I'm jklowden on gitorious.  I will email the @freetds.org
alumni to advise them of the switch.  

2.  How do we coordinate the switch from cvs?  Do we just name, say,
March 15 "Flag Day", and begin using git exclusively from that day
forward? Beware Caesar the Ides of March!  

3.  Am I correct that we no longer need worry about a backup of the
repository, insofar as the one generating the tarballs is an exact copy
of what's on gitorious?  

4.  Would it be wise to also use the overnight process -- perhaps not
*the* overnight process, perhaps another -- to synchronize gitorious
with github?  ISTM that would provide a good backup in the event of,
ahem, a security exploit or a man-made natural disaster like the one
that befell CVS on sf last year.  

--jkl