Hi all!
My highest priority is he upgrade to htmlunit 1.11. A new release after six month makes sense, since many people prefer to deal with a stable binary release, rather then with source code. For instance, the build brakes on my machine because of the incomplete proxy support of Ant's javadoc task. Cheers, Thomas -----Original Message----- From: John and Pip [mailto:[EMAIL PROTECTED] Sent: Dienstag, 20. März 2007 23:13 To: [EMAIL PROTECTED]; Marc Guillemot Subject: Re: [Webtest] WebTest next release: scope and time? Hi Mark and all, +1 for a new release. Main priority htmlunit1.1 and if possible the other dependancies mentioned. Don't personally care about the other items. dna seemed to me to arguing for 2.2 rather than 3, but maybe I misunderstood. I agree that unless there is significant new functionality or a need to rewrite our scripts, should not need to go to 3. Is there either of these? If 3.0 would take some time, what about a 2.2 right now, then target 3.0 next? cheers, John On 3/21/07, Marc Guillemot <[EMAIL PROTECTED] > wrote: This was the question I wanted to ask (to you included ;-)). Everybody agrees or nobody cares? I will start changing target release of all fixed issues since 2.1 to 3.0. Marc. dna wrote: > > Hi > > Isn't there any interest? > > > On 16 mars 07, at 09:17, Marc Guillemot wrote: > >> releases are for WebTest a bit artificial as the latest build is >> (nearly) always the best "release". Nevertheless many people pay high >> attention to official releases and WebTest 2.1 is already 6 months old >> meaning that many improvements have occurred since this time. > > +1 > >> I think that next release's name should be 3.0 rather than 2.2 due >> particularly to WT-232 that bring very significant changes in WebTest >> internals. > > 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. > > > What do you think? > > >> For my part I see currently 3 issues that I want to see fixed >> before the >> next official release: >> >> - Provide a core structure and utility to facilitate WebTest projects >> http://webtest-community.canoo.com/jira/browse/WT-287 >> >> - Upgrade to htmlunit 1.11 >> http://webtest-community.canoo.com/jira/browse/WT-288 >> >> and fix the remaining unwanted differences in generated report due to: >> - Configure steps before execution rather that when added to <webtest> >> http://webtest-community.canoo.com/jira/browse/WT-232 >> >> What do you think? > > Maybe uPgrade all possible dependencies? > A quick look has shown at least log4j and oro could be upgraded. > > Best > dna > > -- > You can sometimes write faster code in C, but > you can always write code faster in Perl. > -- Moral from perlembed > > _______________________________________________ > WebTest mailing list > [email protected] > http://lists.canoo.com/mailman/listinfo/webtest > > -- View this message in context: http://www.nabble.com/WebTest-next-release%3A-scope-and-time--tf3413136.html#a9576474 Sent from the WebTest mailing list archive at Nabble.com. _______________________________________________ WebTest mailing list [email protected] http://lists.canoo.com/mailman/listinfo/webtest
