Snapshots are ok for that, in particular since there is no strong activity
in tomee these days so the snapshot is "stable". It avoids the mess to fork
a project. It created issues with quartz and openjpa by the past when we
did so not sure users like that much at the end.
Very worse case we can
I think we should do a big push to have TomEE 8 out before Oracle Code One.
With that said, we don’t have much time left, and since we still need to wait
for a vote on BVal and TomEE I was trying to cut some time from the TomEE
release if people would look at it now, and then when BVal is ready
Agreed. If there's something that can be done to help them and the time to do
it fits in the target window, that should be the first attempt.
In a rare case a project may even accept help for the actual release.
WebServices project made me committer in 2006 so I could cut Axis 1.4 that was
The primary way should imo ALWAYS to help the other projects we rely on to get
the releases out.
Falling back on a tomee internal release is only a last effort if the other
projects are not responsible.
LieGrue,
strub
> Am 28.09.2018 um 23:50 schrieb David Blevins :
>
>> On Sep 28, 2018, at
> On Sep 28, 2018, at 3:00 AM, Roberto Cortez
> wrote:
>
> While we wait for the official BVal release, I plan do create a preview
> release of TomEE 8 so we can start trying it out and hopefully speed up the
> process. Please, let me know if anyone has any feedback.
As a community we've
