Re: Preparing for 1.7 release

On May 15, 2008, at 6:05 AM, Wolfgang Fahl wrote:

> Dear Russell,
> you wrote:
> > I have now manually converted the change log to release notes. AFAIK
> > the release notes should now be up-to-date.
> That looks great to me.  I'd humbly appreciate if my name would be  
> mentioned in the 1.7 acknowledgment section ...

Done. I wasn't sure what the best way to do this was, as I had only  
acknowledged non-committers in the past.

> > I note, however, that we    now have 12 disabled tests. > This  
> makes me very uncomfortable. I would
> > like to place a priority on fixing those - ahead of addressing any  
> new
> > bug reports, patches, or RFEs; however, as long as we are going to  
> do
> > that, I see no reason that we shouldn't release 1.7 ahead of that.
> The priority setting is fine with me - we could even show the  
> priority in the disabled message by adding a parameter.

I mean that we should not have any disabled tests at all, except under  
extraordinary circumstances - once tests are added, they must be kept  
working, and no tests should be committed unless we can make them pass.


> Also we could not show a message at all for those tests that have to  
> do with the javascript engine. To avoid the counting of theses fully  
> disabled tests we'd e.g. have to refactor the tests with the Junit  
> "suite" approach.

I don't know what you mean, here. Why would javascript tests be  
disabled, and why would we hide that fact.


> > The one big issue that I see is that jdk 1.4 compatibility is  
> broken.
> > We get 36 broken tests, which seems to be related to some changed
> > interfaces. I know that I had gotten that working in the past, and  
> am
> > not sure when it broke. That needs to be the top priority, as we
> > cannot release without it. I am not prepared to drop 1.4 support at
> > this time.
> All of my customers have switched to 1.5. My main product  
> smartGENERATOR does not support 1.4 any more so personally this not  
> much of an issue for me - how about our users base - what percentage  
> do you estimate is still interested in 1.4?

I don't know, but in the past, I have found people often lag the JDK  
releases.

> > What else do we need to do before the release?
> The Tutorial and examples have not been worked on much yet and  
> unfortunately the people having offered to work on it have resigned  
> at least for a few months again.
> I think we should mention that we'd appreciate volunteers working on  
> the improvement and that tutorial improvements are as worthwhile as  
> code improvements.
>

I don't think we need to hold up the release for this, I hope that the  
new release will generate interest in helping with the documentation.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft 
Defy all challenges. Microsoft(R) Visual Studio 2008. 
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

_______________________________________________
Httpunit-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/httpunit-develop