On Mon, Dec 9, 2019 at 3:18 PM Michael Osipov wrote:
>
> Am 2019-12-08 um 18:08 schrieb Elliotte Rusty Harold:
> > Please don't. There are certainly some real and important issues in
> > there. More importantly, users spent a great deal of effort and time
> > to file those. Bulk closing them
Take your time, you have at least three weeks.
Am 2019-12-08 um 18:23 schrieb Tibor Digana:
Hi Michael,
What's up :-)
Thx for making the list of issues.
Pls give me one day to see it completely. I will get back to you tomorrow.
Cheers
Tibor17
On Sun, Dec 8, 2019 at 6:08 PM Elliotte Rusty
Am 2019-12-08 um 18:08 schrieb Elliotte Rusty Harold:
Please don't. There are certainly some real and important issues in
there. More importantly, users spent a great deal of effort and time
to file those. Bulk closing them tells those users we don't value
their feedback or effort. It is useful
The community has no/few resources thus for sure we need to think to it
first.
If we change the current setup and make it too complex we know that it will
be useless and people won't use it (I'm sure that Jason isn't the only one
to have done such kind consultancy).
The idea of having
Having some comparison tests might be good to have especially if an old
feature is maintained in the master.
I am not saying that the old behavior was right. A fix can be backported
too.
We should answer some questions before making any decision:
1. Do we have the effort to maintain the old
I agree with what Jason shared.
It's a reality. Probably a sad one but a lot of users are still running on
ancient version of Maven (didn't we have a discussion recently about the
minimum version of Java to support ?)
There are some kind of business where you don't touch what is doing the
job. It
