Re: M2?

Yeah, it is supposed to be empty, as the last voted release moves to =
/release for publishing:

svn mv https://dist.apache.org/repos/dist/dev/cayenne/X.X \
       https://dist.apache.org/repos/dist/release/cayenne/


> On Jun 11, 2026, at 2:21=E2=80=AFPM, Michael Gentry =
<[email protected]> wrote:
>=20
> OK, I'm a little confused by the SVN steps. Am I supposed to checkout
> https://dist.apache.org/repos/dist/dev/cayenne/ and commit the =
artifacts
> there? I did that and nothing is currently there.
>=20
> Thanks,
> mrg
>=20
>=20
> On Thu, Jun 11, 2026 at 1:13=E2=80=AFPM Michael Gentry =
<[email protected]> wrote:
>=20
>> Yeah, I'm officially giving up on Windows for now. Tried many times =
and
>> never got a clean build on it. I'm switching back to Mac and Linux =
builds
>> now. Hopefully that will be done within a few hours.
>>=20
>> On Thu, Jun 11, 2026 at 7:57=E2=80=AFAM Andrus Adamchik =
<[email protected]>
>> wrote:
>>=20
>>> Hey Mike, so what do you think of Nikita's idea of publishing the =
release
>>> sans Windows, and he'd do the Windows piece?
>>>=20
>>>=20
>>>> On Jun 9, 2026, at 8:06=E2=80=AFAM, Nikita Timofeev =
<[email protected]>
>>> wrote:
>>>>=20
>>>> For the Gradle build I can only think that the Gradle folder is =
missing
>>>> from the source folder. That's the limitation of the Apache =
process, you
>>>> need to remember to copy it every time you grab a clean sources
>>> assembly.
>>>>=20
>>>> Alternatively, I could try to do Win build on my side. If you =
commit the
>>>> sources package with the signatures to the SVN, I can build the =
Windows
>>>> assembly on my machine and commit it back with my signatures. I =
think it
>>>> should be ok to have different signatures in one release as long as =
they
>>>> are in the KEYS file.
>>>>=20
>>>> On Mon, Jun 8, 2026 at 9:24=E2=80=AFPM Andrus Adamchik =
<[email protected]>
>>> wrote:
>>>>=20
>>>>> Interesting... I haven't tried an "src" build. But what I did =
worked
>>> for
>>>>> me on an Azure VM:
>>>>>=20
>>>>> 1. cmd instead of PowerShell
>>>>> 2. git clone [repo] with no extra args like --depth
>>>>> 3. mvn clean verify -P assembly,windows
>>>>>=20
>>>>> All the differences with your recipe are cosmetic though and =
should not
>>>>> affect Gradle. So not sure.
>>>>>=20
>>>>> Andrus
>>>>>=20
>>>>>=20
>>>>>> On Jun 8, 2026, at 12:48=E2=80=AFPM, Michael Gentry =
<[email protected]>
>>> wrote:
>>>>>>=20
>>>>>> OK, installed Win10 in VB (a soul-crushing experience) along with
>>> Java,
>>>>>> Git, Maven, etc...
>>>>>>=20
>>>>>> I was able to clone the repo (using PowerShell):
>>>>>>=20
>>>>>> PS > git clone https://gitbox.apache.org/repos/asf/cayenne.git
>>> --branch
>>>>>> "cayenne-parent-5.0-M2" --depth 1 cayenne-m2-rel
>>>>>>=20
>>>>>> This repeatedly fails, though:
>>>>>>=20
>>>>>> PS > mvn clean install -P"assembly,src"
>>>>>>=20
>>>>>>> Task :pluginUnderTestMetadata
>>>>>>> Task :processTestResources
>>>>>>> Task :testClasses
>>>>>>> Task :test
>>>>>> OpenJDK 64-Bit Server VM warning: Sharing is only supported for =
boot
>>>>> loader
>>>>>> classes because bootstrap classpath has been appended
>>>>>>=20
>>>>>>=20
>>>>>>> Task :test
>>>>>>=20
>>>>>> DbImportIT > simpleDbTaskSuccess() FAILED
>>>>>>  org.junit.platform.commons.JUnitException at ArrayList.java:1596
>>>>>>      Caused by: java.io.IOException at ForEachOps.java:184
>>>>>>=20
>>>>>> DbImportIT > withProjectTaskSuccess() FAILED
>>>>>>  org.junit.platform.commons.JUnitException at ArrayList.java:1596
>>>>>>      Caused by: java.io.IOException at ForEachOps.java:184
>>>>>>=20
>>>>>> DbImportIT > excludeRelDbTaskSuccess() FAILED
>>>>>>  org.junit.platform.commons.JUnitException at ArrayList.java:1596
>>>>>>      Caused by: java.io.IOException at ForEachOps.java:184
>>>>>>=20
>>>>>> GradlePluginIT > gradleVersionsCompatibility() FAILED
>>>>>>  org.junit.platform.commons.JUnitException at ArrayList.java:1596
>>>>>>      Caused by: java.io.IOException at ForEachOps.java:184
>>>>>>=20
>>>>>> 36 tests completed, 4 failed
>>>>>>=20
>>>>>>> Task :test FAILED
>>>>>>=20
>>>>>>=20
>>>>>> Any ideas what might cause the build to fail in the Gradle Plugin
>>> tests?
>>>>>> JDK 21 and latest Maven 3.9.
>>>>>>=20
>>>>>> Thanks,
>>>>>> mrg
>>>>>>=20
>>>>>>=20
>>>>>> On Sun, Jun 7, 2026 at 8:46=E2=80=AFPM Michael Gentry =
<[email protected]>
>>>>> wrote:
>>>>>>=20
>>>>>>> I found an old Win10 ISO. I'll try installing in VirtualBox, =
etc.
>>>>>>>=20
>>>>>>> On Sun, Jun 7, 2026 at 11:14=E2=80=AFAM Andrus Adamchik =
<[email protected]
>>>>=20
>>>>>>> wrote:
>>>>>>>=20
>>>>>>>> Yeah, I think this one actually requires Windows. In the past =
I'd
>>> run
>>>>> it
>>>>>>>> locally via VirtualBox. These days, I simply go to Azure and =
spin
>>> up a
>>>>> VM
>>>>>>>> for a few hours.
>>>>>>>>=20
>>>>>>>> Andrus
>>>>>>>>=20
>>>>>>>>> On Jun 6, 2026, at 5:14=E2=80=AFPM, Michael Gentry =
<[email protected]>
>>>>> wrote:
>>>>>>>>>=20
>>>>>>>>> BTW...
>>>>>>>>>=20
>>>>>>>>> How do I do this step?
>>>>>>>>>=20
>>>>>>>>> # You will need to do this on Windows
>>>>>>>>> mvn clean package -Passembly,windows -DskipTests
>>>>>>>>>=20
>>>>>>>>> I've only got Mac and Linux.
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>> On Sat, Jun 6, 2026 at 4:37=E2=80=AFPM Michael Gentry =
<[email protected]
>>>>=20
>>>>>>>> wrote:
>>>>>>>>>=20
>>>>>>>>>> OK, more updates...
>>>>>>>>>>=20
>>>>>>>>>> In my ~/.m2/settings.xml file, I changed:
>>>>>>>>>>=20
>>>>>>>>>> <id>apache.releases.https</id>
>>>>>>>>>>=20
>>>>>>>>>> to:
>>>>>>>>>>=20
>>>>>>>>>> <id>apache-releases</id>
>>>>>>>>>>=20
>>>>>>>>>> That allowed the mvn release:perform step to run and =
complete. I
>>> had
>>>>>>>>>> gotten apache.releases.https from one of the Apache pages on
>>> setting
>>>>>>>> up GPG
>>>>>>>>>> and my settings file.
>>>>>>>>>>=20
>>>>>>>>>> Starting the rest now...
>>>>>>>>>>=20
>>>>>>>>>> On Wed, Jun 3, 2026 at 9:20=E2=80=AFPM Michael Gentry <
>>> [email protected]>
>>>>>>>> wrote:
>>>>>>>>>>=20
>>>>>>>>>>> I switched to using the ASF Git and made it further, but am
>>> having
>>>>>>>> issues
>>>>>>>>>>> publishing the artifacts (public key) using mvn =
release:perform
>>>>>>>> step...
>>>>>>>>>>> I'll try to get that ironed out Thursday...
>>>>>>>>>>>=20
>>>>>>>>>>> mrg
>>>>>>>>>>>=20
>>>>>>>>>>>=20
>>>>>>>>>>> On Wed, Jun 3, 2026 at 8:16=E2=80=AFAM Nikita Timofeev <
>>>>>>>> [email protected]>
>>>>>>>>>>> wrote:
>>>>>>>>>>>=20
>>>>>>>>>>>> You can check if your GitHub ID is linked with your Apache
>>> account
>>>>>>>> in the
>>>>>>>>>>>> https://gitbox.apache.org self service. Other than that I =
don't
>>>>> have
>>>>>>>>>>>> many
>>>>>>>>>>>> ideas about what to check.
>>>>>>>>>>>> If your access continues to fail, I can proceed with this
>>> release
>>>>>>>>>>>> tomorrow.
>>>>>>>>>>>>=20
>>>>>>>>>>>> On Tue, Jun 2, 2026 at 10:11=E2=80=AFPM Michael Gentry <
>>>>> [email protected]>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>=20
>>>>>>>>>>>>> I'm still getting errors about not having access to
>>> apache/cayenne
>>>>>>>> on
>>>>>>>>>>>>> GitHub. Should I try using the ASF Git repo? Or should =
someone
>>>>> else
>>>>>>>>>>>> take
>>>>>>>>>>>>> over until I can resolve my environmental issues?
>>>>>>>>>>>>>=20
>>>>>>>>>>>>> On Mon, Jun 1, 2026 at 9:09=E2=80=AFPM Michael Gentry <
>>>>> [email protected]>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>=20
>>>>>>>>>>>>>> Thanks for the tips, Nikita.
>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>> I'm going to revert the changes and try again. I'll =
update
>>> with
>>>>> how
>>>>>>>>>>>> far I
>>>>>>>>>>>>>> get.
>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>> On Mon, Jun 1, 2026 at 8:20=E2=80=AFAM Nikita Timofeev <
>>>>>>>>>>>>> [email protected]>
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>> Hi Michael.
>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>> The instructions should be good overall, I use them =
verbatim
>>>>> every
>>>>>>>>>>>> time.
>>>>>>>>>>>>>>> What's definitely missing are the common problems and =
how to
>>> fix
>>>>>>>>>>>> them.
>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>> Usually I go with `mvn release:rollback` first.
>>>>>>>>>>>>>>> If `rollback` can't run (likely because there is no =
release
>>>>>>>>>>>>> descriptor), I
>>>>>>>>>>>>>>> manually revert the commit performed by the `prepare` =
stage.
>>>>>>>>>>>>>>> Then check if the tags are still present and remove both
>>> local
>>>>> and
>>>>>>>>>>>>> remote
>>>>>>>>>>>>>>> if they exist.
>>>>>>>>>>>>>>> Once everything is reverted I start `release:prepare` =
again.
>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>> If `release:perform` fails too, I try to repeat it =
first,
>>>>>>>> sometimes
>>>>>>>>>>>> it's
>>>>>>>>>>>>>>> just a nexus timeout or something.
>>>>>>>>>>>>>>> If the error persists I just repeat the same rollback ->
>>> prepare
>>>>>>>> ->
>>>>>>>>>>>>>>> perform
>>>>>>>>>>>>>>> cycle.
>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>> Hope this helps. Tell me if you need some more info or
>>> support.
>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>> On Mon, Jun 1, 2026 at 12:02=E2=80=AFAM Michael Gentry <
>>>>>>>> [email protected]
>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>> Sadly, still broken for me.
>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>> On Sun, May 31, 2026 at 2:40=E2=80=AFPM Andrus Adamchik =
<
>>>>>>>>>>>> [email protected]>
>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>> This worked for me, so I deleted the tag:
>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>> git push origin :cayenne-parent-5.0-M2
>>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>> - [deleted]             cayenne-parent-5.0-M2
>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>> Maybe it will work now for you, that the old tag is =
gone?
>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>> Andrus
>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>> On May 31, 2026, at 2:31=E2=80=AFPM, Michael Gentry <
>>>>>>>>>>>> [email protected]>
>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>> This command failed on me:
>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>> mvn release:prepare -DpreparationGoals=3D"clean =
install"
>>>>>>>>>>>>>>>>>> -DautoVersionSubmodules=3Dtrue
>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>> I worked past the error and ran the command again, =
but it
>>>>>>>>>>>> failed
>>>>>>>>>>>>>>>> because
>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>> couldn't create the tag because the tag already =
exists.
>>>>>>>>>>>> Somehow it
>>>>>>>>>>>>>>>>> created
>>>>>>>>>>>>>>>>>> the tag. So, I tried deleting the tag, but now I'm
>>> getting:
>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>> [mrg@odin 14:15:58] ~/Projects/cayenne master> git =
push
>>>>>>>>>>>> origin
>>>>>>>>>>>>>>>>>> :cayenne-parent-5.0-M2
>>>>>>>>>>>>>>>>>> ERROR: Permission to apache/cayenne.git denied to =
mrg.
>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>> Same error when I use:
>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>> git push --delete origin cayenne-parent-5.0-M2
>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>> Any suggestions? Or does someone else have a smoother
>>> path to
>>>>>>>>>>>> take
>>>>>>>>>>>>>>>> over?
>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>> mrg
>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>> PS. The tag got created when I had used HTTPS as the =
clone
>>>>>>>>>>>>> method. I
>>>>>>>>>>>>>>>>>> couldn't delete the tag that way, either (GitHub =
doesn't
>>>>>>>>>>>> support
>>>>>>>>>>>>>>>>> user/pass
>>>>>>>>>>>>>>>>>> credentials), so I deleted the repo and checked out =
using
>>>>> SSH,
>>>>>>>>>>>>>>> which is
>>>>>>>>>>>>>>>>>> when I get the permissions error.
>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>> On Sun, May 31, 2026 at 1:29=E2=80=AFPM Michael =
Gentry <
>>>>>>>>>>>>> [email protected]
>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>> Hi Andrus, I'm working on it. Trying to resolve =
errors. I
>>>>>>>>>>>> suspect
>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>> release guide is a little bit out of date.
>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>> On Sun, May 31, 2026 at 9:20=E2=80=AFAM Andrus =
Adamchik <
>>>>>>>>>>>>>>> [email protected]>
>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>> Hey Mike, wanted to check how things are going with =
the
>>>>>>>>>>>> release.
>>>>>>>>>>>>>>>> Eager
>>>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>>>>>> start using M2 and committing more cleanup code :)
>>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>> If you don't have time for it now, not a problem =
too.
>>> Just
>>>>>>>>>>>> let
>>>>>>>>>>>>> us
>>>>>>>>>>>>>>>> know.
>>>>>>>>>>>>>>>>>>>> Nikita and myself should be able to jump in.
>>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>> Andrus
>>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>>> On May 25, 2026, at 8:06=E2=80=AFPM, Michael =
Gentry <
>>>>>>>>>>>>> [email protected]
>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>>> I should be able to start it Tuesday afternoon.
>>>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>>> On Sun, May 24, 2026 at 5:47=E2=80=AFPM Andrus =
Adamchik <
>>>>>>>>>>>>>>>> [email protected]>
>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>>>> I think at this point we are ready to release M2. =
It
>>> has
>>>>> a
>>>>>>>>>>>>> huge
>>>>>>>>>>>>>>> new
>>>>>>>>>>>>>>>>>>>> scope
>>>>>>>>>>>>>>>>>>>>>> - a complete new agentic coding stack.
>>>>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>>>> Mike, do you still have time to prepare the =
release?
>>>>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>>>>> Andrus
>>>>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>>>>> On Apr 17, 2026, at 11:00=E2=80=AFAM, Michael =
Gentry <
>>>>>>>>>>>>>>> [email protected]
>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>>>>> Hi Nikita,
>>>>>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>>>>> I don't think there is an urgency to get M2 out, =
so
>>> if
>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>> outstanding
>>>>>>>>>>>>>>>>>>>>>> PRs
>>>>>>>>>>>>>>>>>>>>>>> make sense to include in M2, I think it is OK to
>>> wait on
>>>>>>>>>>>>> them.
>>>>>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>>>>>> mrg
>>>>>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>>>>> On Tue, Apr 14, 2026 at 8:18=E2=80=AFAM Nikita =
Timofeev <
>>>>>>>>>>>>>>>>>>>>>> [email protected]>
>>>>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>>>>>> Several PRs are waiting for me, but nothing is =
too
>>>>>>>>>>>> critical,
>>>>>>>>>>>>>>> so
>>>>>>>>>>>>>>>> we
>>>>>>>>>>>>>>>>>>>> may
>>>>>>>>>>>>>>>>>>>>>> go
>>>>>>>>>>>>>>>>>>>>>>>> ahead with M3.
>>>>>>>>>>>>>>>>>>>>>>>> Instructions are all good, I use them every =
time.
>>>>>>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>>>>>> On Tue, Apr 14, 2026 at 2:37=E2=80=AFAM Andrus =
Adamchik <
>>>>>>>>>>>>>>>>> [email protected]
>>>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>>>>>>>> I just filed all my taxes
>>>>>>>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>>>>>>> Congrats! Which reminds me - I am still =
waiting
>>> for my
>>>>>>>>>>>>>>> numbers
>>>>>>>>>>>>>>>>> from
>>>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>>>>>>> accountants :)
>>>>>>>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>>>>>>>> so I have some free cycles now if there is
>>>>>>>>>>>>>>>>>>>>>>>>>> anything I can do to help.
>>>>>>>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>>>>>>> How about publishing the release. @Nikita - do =
you
>>>>> have
>>>>>>>>>>>>>>> anything
>>>>>>>>>>>>>>>>> in
>>>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>>>>>>> queue we'd need to deal with before M2 that =
can't
>>> be
>>>>>>>>>>>> moved
>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>> M3?
>>>>>>>>>>>>>>>>>>>> Also
>>>>>>>>>>>>>>>>>>>>>>>>> anything missing in the release instructions =
at
>>>>>>>>>>>>>>>>>>>>>>>>> =
https://cayenne.apache.org/dev/release-guide.html
>>> ?
>>>>>>>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>>>>>>> Andrus
>>>>>>>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>>>>>>>> On Apr 13, 2026, at 6:16=E2=80=AFPM, Michael =
Gentry <
>>>>>>>>>>>>>>>> [email protected]
>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>>>>>>>> I just filed all my taxes, so I have some =
free
>>> cycles
>>>>>>>>>>>> now
>>>>>>>>>>>>> if
>>>>>>>>>>>>>>>>> there
>>>>>>>>>>>>>>>>>>>> is
>>>>>>>>>>>>>>>>>>>>>>>>>> anything I can do to help.
>>>>>>>>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>>>>>>>> On Mon, Apr 13, 2026 at 5:08=E2=80=AFPM =
Andrus Adamchik <
>>>>>>>>>>>>>>>>>>>> [email protected]>
>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>>>>>>>>> Not too many significant new features in M2 =
so
>>> far,
>>>>>>>>>>>>> though
>>>>>>>>>>>>>>>>> quite a
>>>>>>>>>>>>>>>>>>>>>> few
>>>>>>>>>>>>>>>>>>>>>>>>> bug
>>>>>>>>>>>>>>>>>>>>>>>>>>> fixes. So yeah, we probably should do it.
>>>>>>>>>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Apr 13, 2026, at 4:45=E2=80=AFPM, =
Michael Gentry <
>>>>>>>>>>>>>>>>> [email protected]
>>>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>>>>>>>>>> Is it time for a 5.0.M2?
>>>>>>>>>>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>>>>>>>>>> I noticed the M1 was released 2024-09-09 =
and
>>> that
>>>>>>>>>>>> seems
>>>>>>>>>>>>> a
>>>>>>>>>>>>>>>> long
>>>>>>>>>>>>>>>>>>>> time
>>>>>>>>>>>>>>>>>>>>>>>>>>> ago...
>>>>>>>>>>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>>>>>>>>>>> mrg
>>>>>>>>>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>>>>> Best regards,
>>>>>>>>>>>>>>>>>>>>>>>> Nikita Timofeev
>>>>>>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> Best regards,
>>>>>>>>>>>>>>> Nikita Timofeev
>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>=20
>>>>>>>>>>>>=20
>>>>>>>>>>>>=20
>>>>>>>>>>>> --
>>>>>>>>>>>> Best regards,
>>>>>>>>>>>> Nikita Timofeev
>>>>>>>>>>>>=20
>>>>>>>>>>>=20
>>>>>>>>=20
>>>>>>>>=20
>>>>>=20
>>>>>=20
>>>>=20
>>>> --
>>>> Best regards,
>>>> Nikita Timofeev
>>>=20
>>>=20