If enabled by default, please offer a reliable way for applications to disable it. We don't need it for JOSM, and we have been so impacted with jaw's problems in the past years that we will never want it enabled by default for us.
Le dim. 7 avr. 2019 à 12:08, Samuel Thibault <sthiba...@debian.org> a écrit : > Hello, > > Matthias Klose, le sam. 06 avril 2019 15:46:21 +0200, a ecrit: > > On 06.04.19 15:13, Paul Gevers wrote: > > > We're late already, I would want this rather sooner than latter > > > in buster, such that there is some real live testing before we release. > > > Sure, there are chances for bugs, but if that's the case, let's find > > > them and fix them. > > > > I disagree. I'll do the next upload with Samuel's proposed patches, not > > enabling that by default, together with the planned security update. > Then > > people can start testing if the wrapper works. > > Well, I'm afraid that what will happen is that the people who will > test will simply find out that it just works for them (just like it > does already for them with openjdk-8) ; will we then conclude near the > release that it should be enabled by default for Buster, and then be hit > by the much wider exposition to jaw? > > If on the contrary we enable it by default during the freeze, we will > have *way* more testing coverage, and thus be much more confident with > keeping it enabled by default in Buster if we don't see bug reports. > > > Enabling features during the freeze which were broken most of the time > > during the development cycle sounds risky. > > Just ftr: what was broken was the load of jaw in openjdk-11, jaw itself > seems to work in openjdk-8 for people needing it. > > Samuel >
