Am 27.05.21 um 19:38 schrieb Matthias Seidel:
Am 27.05.21 um 19:10 schrieb Marcus:
Am 27.05.21 um 16:18 schrieb Matthias Seidel:
Am 27.05.21 um 16:07 schrieb Dave Fisher:
IMO there are a couple more issues like hyperlink protocols to
always allow to look into before 4.1.11 builds. So, if you are
looking to build right now then 4.2.0dev.

Yes, 4.2.0-Dev3 would simply be an official "snapshot" of what we have
in branch AOO42X.

4.1.11 needs a lot more work to be released.

Maybe a thread on the release blockers for 4.2.0?


please not as mails. IMHO this will end in a total mess and nobody is
able to keep the overview. ;-)
Good idea!

Better to create a Confluence page, start with the list of opened and
targeted issues [1]. Then we can discuss which issues we can fix for

I would simply start with the list of Release Blockers:

I've started this list:

Will now add the classified blockers also.




On May 27, 2021, at 6:41 AM, Matthias Seidel
<> wrote:
Am 27.05.21 um 15:38 schrieb Jim Jagielski:
On May 21, 2021, at 5:02 AM, Matthias Seidel
<> wrote:
Am 14.05.21 um 18:56 schrieb Jim Jagielski:
On May 14, 2021, at 1:27 AM, Arrigo Marchiori
<> wrote:

I agree, but how many 4.1.X versions do we want to publish
before 4.2.0?
Now that we support two digits, please let us not point to
4.1.99 ! ;-)

FWIW, I tend to agree. We fixed the bug. Maybe its not the best
solution, but I don't see why we should continue to "focus" on
4.1.X at the expense of 4.2.X.
We already made some progress on the Release Blockers for 4.2.0.
But the remaining ones are untouched for long time.

What about a 4.2.0-Dev3? We already planned it when 4.1.10 got

So should the push be 4.1.11 or 4.2.0-Dev3?
I don't see a problem to do both?

To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to