+1 definitely agree on that let's make it simple.... simple deploy of one build with java8 and voila. it's snapshot and NOT a release... so we do not have to jump on every bugs immediately. It will be already a great forward to have quick feedback from maven consumers....
On Mon, 13 May 2019 at 02:43, Mickael Istria <mist...@redhat.com> wrote: > IMO, if some patch managed to get to master, it's worth being released, > even if IT test fail. > So I would make the first step being a `mvn deploy` of what[s in master, > before running other tests. > I think this would be much simpler, allow community to test some "master" > snapshot even if it's bugged (so community can help in resolving), and > would cover all use-cases I have about snapshot. And -to put it another > way- making complex effort to run IT tests on all OS before publishing a > snapshot is over-engineering. > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
