yade-dev team mailing list archive

[Janek Kozicki <janek_listy@xxxxx>]

I'm forwarding this to mailing list, because it was quite important on what to do.

Begin forwarded message:

Date: Sat, 14 May 2005 08:32:34 +0200
From: Olivier Galizzi <olivier.galizzi@xxxxxxx>
To: Janek Kozicki <janek@xxxxxxxxxx>
Subject: Re: tags

Janek Kozicki wrote:

>I want to make some tags to produce some version numbers.
>
>I'll go through all our revisions, and make tags for revisions, that
>have introduced something new.
>
>I'm not sure how to number all those versions. Maybe I'll see when I'll
>dig through revisions to see what changes were done.
>
>
>Let's say, that our three-numbers version numbering will be following:
>
>
>release_number . major_revision_number . minor_revision_number
>
>so for example, yade 0.1.3 is:
>
>0 - not released yet
>1 - first major revision
>3 - third minor revision
>
>
Yes that sounds good.

>
>- Perhaps introducing FEM will be one major revision number. 
>
>- Mabye when we will have coupling between FEM and DEM it will be
>another major revision number.
>
>- When we will have your tetrahedrons - it will be another major
>revision number.
>
>- When we will have lattice model - another major revision number.
>
>- Switching from old directory tree, to new directory tree perhaps can
>be another major revision number - exactly what you have done now.
>
>- And when we split this directory tree from single kdevelop project to
>all those 24 separate kdevelop projects - it will be another major
>revision number.
>
>
>In total we should end up having around 7 or 12 major revision numbers.
>
Yes, yes ,yes ,yes ,yes and yes !! :)

>Of course we can decide for example to make release number 1 before
>coupling FEM and DEM, or before you do tetrahedrons - just as you
>prefer. In fact FEM+DEM will be just another major revision number,
>independent from release number.
>
>
>I think that maybe release 1 should be after we decide on names for ALL
>classess, directories, function names, and when we finish splitting that
>into separate kdevelop projects. And maybe something more. Of course we
>will have to wait more time to make this release - maybe we will do it
>around the time when you will defend your PhD ?
>
>  
>
Yes, at least we have to make this splitting before releasing version 1.

>So I want to make some tags, and how do you think - how far I could go now?
>
>0.3.5 or 0.5.1 or maybe 0.7.14 ??? tell me what you think. In my opinion
>somewhere between 0.6.? and 0.8.? should be OK.
>
>
>I also think that for example tag that has currently number 0.1.6 will
>become 0.2.something, or maybe even 0.3.something. Becauase we have made
>at least once a major change in design since we started 6 months ago, so
>it should be major revision number increment.
>
>
>
>And another question - do you want to keep this directory tree in tags?
>I mean - all major revisions 0.1.? are in directory yade-0.1, all major
>revisions 0.2.? are in directory yade-0.2, and so on?
>
>
>I would prefer to have flat directory here, just because it is faster to
>see them all, and you don't have to click to go inside. On slow internet
>connection (with berlios we have very often slow connection...) it's
>better to not have to click one more time to go into another directory
>(like inside yade-0.1 and yade-0.2 and yade-0.3 ... ), and for each
>major revision number, there won't be big number of minor revisions - I
>think that it will be three minor revisions on average (because I'm too
>lazy to tag everything and produce twenty minor revisions....).
>
>  
>
Yes I also think a flat directory tree is better here.

>I'm sorry that this email is so long :) Think about it, and when you
>will answer I'll start to make tags. :)
>
>
>I hope that in this weekend I'll end all that furniture stuff in my house.
>
>  
>
Ok that good ideas. You can do all what you've said.

Oliv

-- 
Janek Kozicki                                                         |
_______________________________________________
Yade-dev mailing list
Yade-dev@xxxxxxxxxxxxxxxx
http://lists.berlios.de/mailman/listinfo/yade-dev