On 20 mars 07, at 17:41, Marc Guillemot wrote:
I will start changing target release of all fixed issues since 2.1
to 3.0.
Shouldn't major version be used for changes that have major
(prositive or negative...) impacts for the end-user?
Such as a change that could break existing script, as the migration
to htmlunit was, or a change that brings new possibilities.
That way, I could as an end-user better decide if/when I want to
upgrade the webtest version.
A change to a minor version could be done pretty much anytime,
whereas refactoring and testing amay have to be planned along with a
change to a major version.
I would see the use of Ant 1.7, java 1.5, xpath 2.0 or successful
XmlHttpRequest as possible reasons for a webtest 3.
Which changes make this release worth of a 3.0 instead of a 2.2?
If this release is a 3.0, how do we mark the next important change?
What do you think?
dna
--
As far as we know, our computer has never had an undetected error.
-- Weisert
_______________________________________________
WebTest mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/webtest
