Re: [Unichrome-devel] Pre-X.org cleanup.

[Luc V. <li...@sk...>]

On Tue, Sep 14, 2004 at 02:55:24PM +0200, Simon 'corecode' Schubert wrote:
> On 14.09.2004, at 12:53, Luc Verhaegen wrote:
> 
> so plan is that development still takes place at sf.net whereas 
> releases go into x.org? I'm a little bit confused about that and it 
> won't make tracking changes easier. whatsoever, I can't decide on that 
> anyways.
> 
> I'd use versioning like 0.26.1 and in CVS then maybe 0.26.123 (tho 
> updating version in cvs seems pointless, so it could also be 0.26.0), 
> so you can clearly see on which release the CVS is based or vice versa. 
> Then also the release names on sf.net should be adjusted accordingly, 
> so move from r26 to 0.26.1 or so.
> 
> having the same version number scheme in x.org, sf.net cvs and sf.net 
> download page will confuse people much less.
> 
> cheers
>   simon
> 
The way we work here is, broadly, release when we have something to 
release. Our task is to clean up this driver and to add a lot of 
functionality in the process. This needs testing, a lot of testing. 
We should be glad for people testing our code and we shouldn't expect 
everyone to go download CVS every few days. So we try to release 
things as seperate files regularly. These releases also mark a spot 
in time where we try to build against various trees and generally try 
to ascertain that we haven't broken anything (sadly, i'm not always 
that thorough).

We will probably move to x.org, in time, but there is no reason to 
stop unichrome.sf.net right now.

The current plan is to move our releases, after some time, after it 
has seen some testing, into x.org. So keeping the version in sync 
with our release makes good sense. Also, no-one really depends on 
this version, just us. For one, it will help us keep track of what 
version of via driver people are using. This will be quite important 
once code will spread.

We release quite often and our releases actually just are a resync 
with HEAD. But we still need to be able to discern between CVS and 
the releases. 

I do find keeping the release number in HEAD and updating it 
regularly a tad superfluous; if people use CVS, they should use 
recent CVS. This is especially true for a project like ours.

Luc Verhaegen.