On Sunday 10 August 2003 09:05 am, Tuomo Valkonen wrote:
> It's been a while since the previous release as I wanted to freeze the
> Lua configuration/scripting interface for this release and therefore
> finish work on a few things. Well, on my part the interface is frozen,
> but I will still accept constructive complaints for a short time and
> after that the implemented parts of the scripting interface will be
> frozen. But in all likelihood, if no one has anything else to say, but
> "it's ok", "it sucks", the interface will no longer change, only possibly
> grow.
>

Tuomo,

First, let me say that I've used ion off an on for a long time now.  I've been 
away from it for about a year, and let me say that I really like the 
direction that ion is going.  I'm back with this windowmanager to stay!

My suggestion, though, is in order to make it easier to determine when the 
configuration file format changes drastically enough to break backwards 
compatibility you should start marking releases with some sort of release 
number instead of just the date.

For example, you could use a 'config file version' marker in addition to the  
date (ion-devel-20030810-1.3) and make sure that the file formats between 1.3 
and 1.4 are compatible by not completely removing keywords until 1.4.  So if 
some_function gets renamed to some_other_function, both keywords would work 
until the 1.4 config file format is finalized.

The other suggestion is related to something that has already been discussed 
on the list archives, so I will just put it out there and (hopefully) it will 
not start another long discussion -- having CVS branches to make large 
changes on, and merging them into HEAD every now and then.  That way you 
could use major/minor release numbers to track minor config/feature changes, 
and major improvements, etc...

Anyway, thanks for the great WM!

-- 
Mark McCoy -- Sergeant -- 2/7 Cavalry 1CD -- Garry Owen, Hooah!
[EMAIL PROTECTED]
"There are 10 types of people in this world, those who understand binary and
those who don't."


Reply via email to