|
From: Anton A. <ai...@ca...> - 2003-02-21 10:43:57
|
On Fri, 21 Feb 2003, Szakacsits Szabolcs wrote: > On Thu, 20 Feb 2003, Anton Altaparmakov wrote: > > The version in bitkeeper is now changed to 1.7.2-WIP. > [...] > > * We are now on 1.7.2-WIP and want to make a 1.7.2 release. > [...] > > Happy now? > > Don't care about my happiness, care about users' one ;) In general > that makes happy developers as well. > > But I can make my comments, if interested. (Free) software project > management guidelines recommend, among others, internal consistency > and clearly indicating the differences between development and release > versions in the "version numbers". To avoid confusion, also > documenting how the versioning is done. > > Apparently you're using the GNU version numbering (major.minor.patch) > but maybe not, it's not documented. If yes, then the above 1.7.1. -> > 1.7.2 change indicates a "fixing bugs" release. Unfortunately my > forthcoming, potentially very dangerous, ntfsresize with cluster > relocations new code and new NTFS tool[s] don't fit this. I don't think I want to plan ahead that much, i.e. maybe tomorrow someone will email me with a new found bug and I would release 1.7.2 immediately after fixing it. If noone does that and lots of changes have gone in like the ones you plan then the next release would go from 1.7.2-wip to 1.8.0. > About the "WIP" extension in the development(?) tree. I'm afraid it's > uncommon and cryptic for the majority of users. I guess you made this > choise based on e2fsprogs versioning. No, I have no idea of e2fsprogs versioning. WIP is what is used a lot in kernel development so it was natural to for me to take it on. > Considering the aboves and unless you plan a "bug fix" patch level > release, of course providing you're using the GNU version numbering, I > would recommend the usage of 1.8-DEVELOPMENT or 1.8.0-DEVELOPMENT, > clearly indicating the current ntfsprogs state in development. Sounds to me like you actually want a separate development tree which will contain code which is going to destroy people if they use it. I have always aimed to keep my code stable at all times and never have code that would be destructive (apart from bugs I haven't found obviously). I admit there have been short periods where I have said "don't use this it is destructive" but I have always tried to fix them asap... I am going to start a second bitkeeper repository cloned from the parent one, and it will be called ntfsprogs-devel (even though I think that is going to confuse people because one of our rpms is called ntfsprogs-devel and people will get mixed up between the two very badly, especially if someone creates rpms from the devel version!!! there would be an ntfsprogs-devel.rpm from the stable tree, one ntfsprogs-devel.rpm from the development tree and one ntfsprogs-devel-devel.rpm from the development tree. Confused yet? I am...). Thinking about it, having a repository called ntfsprogs-devel is probably a really bad idea... Anyone want to suggest a name for it? The version of the development tree will be "ntfsprogs 1.x+1.y-devel" for a stable version of "ntfsprogs 1.x.y". Then the development repository will be for all experimental code. The only thing to note here is that you will have to mark you patches very clearly as to which repository they should go to. And remember that if I apply something to the stable tree I can use BK to get the same stuff merged into the devel tree but not vice versa, i.e. patches to the devel tree will never make it to the stable tree, except when the devel tree is turned into the stable tree at some point in time for the next big release. As far as versioning is concerned I use major_hi.major_lo.minor as version numbers, i.e. 1.7.1 -> 1.7.2 is minor updates but 1.7.x to 1.8.0 is major updates and after 1.9 will come 2.0 as natural occurence. If something really major happens before 1.9.x is out we may jump to 2.0 already (note really major means a full rewrite of the library or things like that). Best regards, Anton -- Anton Altaparmakov <aia21 at cantab.net> (replace at with @) Linux NTFS maintainer / IRC: #ntfs on irc.freenode.net WWW: http://linux-ntfs.sf.net/ & http://www-stu.christs.cam.ac.uk/~aia21/ |
