[X2go-dev] X2go Git now available at BerliOS

Gerry Reno greno at verizon.net
Fri Jan 7 18:04:45 CET 2011


On 01/07/2011 11:48 AM, Heinz-M. Graesing wrote:
> Hello Gerry,
>
> Awas am 07.01.2011 16:41, schrieb Gerry Reno:
>
>   
>> $ bzr pull
>> Using saved parent location: git://git.berlios.de/x2go
>> No revisions to
>> pull.                                                                                                         
>>
>> $ bzr tags
>> uthoern              6
>> $
>>
>> Mike, yes it pulled a tag.  But what is the definition of this 'uthoern'
>> tag?  A tag usually corresponds to a released version of software and so
>> the tag usually contains the release number, something like 3.0.1-14
>> etc.  How does uthoern corresponds to a x2go release?
>>     
> Uthoern is our actual release by name, not by number. As there are a lot
> of Packages with different version counters you can use with this
> release, it was an idea of me and mike to use the "release name" instead
> of the "version number".
>
> Regards,
>
> Heinz
> _______________________________________________
> X2go-dev mailing list
> X2go-dev at lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/x2go-dev
>
>   

Heinz,
    Ok, but is this really going to work?

    The various components that make up 'all' of x2go should be in their
own project.

    So for example, x2goclient should be a separate project from x2goserver.

    This way each of them can have their own release version numbers.

    If you have the entire x2go under one project then the entire
project, clients, servers, all of it will have a new version number
(tag) each time you release any new part of the codebase.  DVCS operates
on versioning the entire codebase and not on versioning separate files
as was the case with CVS.

    So if you have a stable server, 3.0.1-XX, but you have new clients
coming along and changing, the only way to prevent the server release
from also incrementing is to have the clients and server separated into
separate projects.  And that way each would have their own release
numbering scheme.


Regards,
Gerry





More information about the x2go-dev mailing list