[tei-council] next release

[Syd Bauman]

SR> rolling out a new release involves our friends at Syncrosoft and
SR> so on. its just not "nice" to roll out a new release every 5
SR> minutes.

Only if it is a "major" or "minor" update that involves changes to
the schemas.


LB> [Hard to tell the difference]

I think Lou is absolutely correct that it is sometimes going to be
hard to tell the difference. But whether we use a
"major.minor.bugFix" numbering scheme or two separate branches,
either way we would have to decide for each change which it was. If
we just use sequential version numbers (e.g., the date), we would not
have to figure it out, but then the folks at SyncRO would have to
decide themselves whether an upgrade to their framework was needed.
So that's a bit rude.


> This is that we release 1.0.1 on 1st January, with typos and
> clarifications to the prose _only_, and that we announce this now.

Why would we limit ourselves to prose only? Not that I really have
the wherewithal to do much else right now, it seems like a pretty
artificial restriction. If there's an error to be fixed, it should be
fixed, and users should be able to get it via the release mechanism.

My suggestion is:
* one branch, unless major project requires another
* new release 2008-01-01 (or thereabouts), no restriction on typos
  only 
* new release scheduled for each quarter thereafter (01-01, 04-01,
  07-01, 10-01) annually
* it is possible that there have been *no* changes to the Guidelines
  in a quarter, in which case no new release is needed, but notice of 
  that fact should be posted where releases go (i.e. Sourceforge),
  mentioned on TEI-L, etc.