Skip to Content.
Sympa Menu

freetds - Re: [freetds] status of snapshots

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: Andy Wakefield <a_wake AT earthlink.net>
  • To: FreeTDS Development Group <freetds AT lists.ibiblio.org>
  • Subject: Re: [freetds] status of snapshots
  • Date: Sat, 09 Apr 2011 14:22:10 -0400

James,

Your hard work is very, very much appreciated. Thanks for all you do to
maintain this excellent software!

--
Andy Wakefield
a_wake AT earthlink.net

-----Original Message-----
From: James K. Lowden <jklowden AT freetds.org>
Reply-to: FreeTDS Development Group <freetds AT lists.ibiblio.org>
To: freetds AT lists.ibiblio.org
Subject: Re: [freetds] status of snapshots
Date: Sat, 9 Apr 2011 10:35:46 -0400


On Fri, 8 Apr 2011 23:58:50 -0400
"James K. Lowden" <jklowden AT freetds.org> wrote:

> Snapshots are currently broken. That includes the automatically
> generated nightly snapshot for CVS HEAD and for the patched version of
> the release (0.82). It is also why there's no release candiate yet.

Snapshots are currently working. That includes the automatically
generated nightly snapshot for CVS HEAD and for the patched version of
the release (0.82). And we have a release candidate, correctly
spelled after a night's sleep.

Automake, to their credit, documented what to do, even hinted at a
couple of ways to do it. And the new doc/Makefile.am is just a little
easier to maintain.

The nightly build and versioning system is due for change. Soon you
will see:

1. The HEAD version -- 0.xx.dev.yyyymmdd -- will instead become
0.xx.dev.n, where n increases monotonically with each day for which
there's a commit to CVS.

2. The stable version -- soon to be 0.91.0 -- will likewise
automatically increment each day there's a commit to CVS.

3. The best way to know when a particular version was released is to
look at ChangeLog. However, that's not much use for when looking at a
binary if you don't have ident(1). The nightly build system will do
something to maintain a database of version numbers and dates, probably
by adding a table to the website. (There's a chicken-and-egg problem
keeping version data in CVS.)

We plan to drop CVS, and Sourceforge, probably in favor of git on
github. Your Late Bronze Age maintainer is, really, just fine with CVS
and not especially eager to spend time learning yet another metatool.
If the choice makes a difference to you, this would be a good time to
say so.

Your humble maintainer,

--jkl

_______________________________________________
FreeTDS mailing list
FreeTDS AT lists.ibiblio.org
http://lists.ibiblio.org/mailman/listinfo/freetds




Archive powered by MHonArc 2.6.24.

Top of Page