[Monotone-devel] interface version / command matrix

[Thomas Keller]

Hi!

I just started on

http://venge.net/mtn-wiki/AutomateVersions

This gives you a fast overview which interface versions belong to which 
version of monotone and also which interface version added / changed 
which commands.

One can - of course - get these data by looking into the appropriate 
manual sections or query old versions of cmd_automate.cc / automate.cc 
each time, but the problem is that all these might be sometimes not 100% 
correct (see my fix in 7c139828f93 f.e.).

As you can see in the matrix it was quite common that we went away from 
our minor/major increment rules in the past because nobody or everybody 
felt responsible to change interface_version in cmd_automate.cc, 
practically leading to a mess for the next release.

Now, a simple new rule could be: Whenever you touch an existing automate 
command, also mark it as changed ("C") on this wiki page for the next 
upcoming interface version (which would then either be 7.1 or 8.0). The 
release coordinator then looks at the page and if he only encounters 
"A"'s in a col, he'd do a minor increment, however if he encounters at 
least one "C" in the column, he'd do a major increment.

I'm still undecided if / how we can handle "collateral" changes, like 
f.e. Derek's recent change wrt --depth option  handling. This - 
theoretically - alters the output for at least two automate commands 
(inventory and get_current_revision), which might expect a definite 
output for a certain input.

Opinions?

Thomas.

--
GPG-Key 0x160D1092 | address@hidden | http://thomaskeller.biz
Please note that according to the EU law on data retention, information
on every electronic information exchange might be retained for a period
of six months or longer: http://www.vorratsdatenspeicherung.de/?lang=en

signature.asc
Description: OpenPGP digital signature