I'm seeing some test failures on Windows. I've started to set up a Jenkins build to be able to catch these. (at present the failure mails are sent direct to me)
Depending on the cause, the failures need to be fixed before the next release. On 11 February 2017 at 10:22, Philippe Mouawad <philippe.moua...@gmail.com> wrote: > Hello, > Since our discussion on "Release a 3.2 ?" , trunk has nicely evolved: > > - 33 Enhancements > - 25 bug fixes > > I think we can now plan a release. > > I see the following remaining work: > > - Ensure the migrated docs (from PDF) do not contain old "Urban legends" > :-) nor bad practices. Those are the 4 Tutorial links in left menu. It > would be nice to review them. I've fixed some but not done the full work > - Fill in introduced properties in properties_reference.xml > - If possible add JUnits on the regression introduced in GET with no > body (see my mail) > - Fill in New and Noteworthy section > > > > -- > Cordialement. > Philippe Mouawad.
