[Webtest] Canoo release number
Daniel Sheppard
webtest@lists.canoo.com
Mon, 1 Sep 2003 15:08:05 +1000
Going a bit devil's advocacy here.
> +) Everyone uses a different build of Canoo WebTest depending=20
> on the time of the last download.
A build is only posted once a change is made, so it's not quite so extrem=
e as that. If it's important that you have the same build as somebody, wh=
y don't you get their build off them?=20
What you're asking for here is either:
a) Longer between releases - this is A BAD THING, I hope you know why.
b) The ability to get old releases - this would be a good thing.=20
However, I don't see how either are related to the build number/version n=
umber question.
> +) What has changed between two builds?!
This is a bit of a problem in documentation, completely unrelated to the =
build number/version number question. Having:
300 - Did blah
301 - Did blag=20
302 - Did bleg
Is completely equivalant to:
3.0.0 - Did blah
3.0.1 - Did blag
3.0.2 - Did bleg
As long as there's a changelog somewhere, would there be a problem? (I se=
em to remember there being a changelog for the last 4-5 builds being on t=
he canoo webpage... maybe under the news section there was build numbers =
instead of dates?)
Having the release dates for the various builds would be useful also.
> +) What are the exact versions of the required JARs ...=20
> welcome the JAR hell
> ... :-)
I don't see how this is related at all either. In fact, I'm not sure I'm =
even understanding your problem. Is it that the versions that webtest rel=
y on aren't documented or is it that other projects would be unable to sa=
y "Relys on canoo versions x, y, z".
But aside from that, if a version number scheme were adopted, I would pro=
pose:
major.minor.patch
patch changes every build
minor changes whenever an existing test has to be modified.
major changes whenever an existing test is broken beyond repair.
Daniel Sheppard
http://freeroller.net/page/soxbox=20
#########################################################################=
############
This email has been scanned by MailMarshal, an email content filter.
#########################################################################=
############