I am +1 as well. On Mon, Jun 22, 2026 at 12:02 PM Michael Gentry <[email protected]> wrote:
> I've updated my scripts that check for files that aren't properly licensed > and saw the two I missed before. I think these can be fixed for the next > release. > > Everything checks out on my end, so I'm also a +1. > > Thanks, > mrg > > > On Mon, Jun 15, 2026 at 6:14 AM Nikita Timofeev <[email protected] > > > wrote: > > > +1 > > > > - sources parity - good > > - signatures - good (Windows assembly is signed with my key) > > - full build from sources - good > > - MacOS Modeler and MCP - runs on MacOS, JDK 25 > > - Generic Modeler and MCP - runs on MacOS, JDK 25 and 21 > > - Windows Modeler - runs on Windows 11, JDK 25 unsupported, only JDK 21 > > checked > > - RAT - missing headers in TestMcpServer.java and in > > org.slf4j.spi.SLF4JServiceProvider > > (we have headers in other providers). Good enough for the milestone > > release, it may be fixed later. > > - Staging Maven repo - good, verified with a demo project > > > > Also a note about the RAT: a bunch of new `.md` files are not excluded, > > need to fix config. > > > > > > On Sun, Jun 14, 2026 at 8:01 PM Andrus Adamchik <[email protected]> > > wrote: > > > > > Ok, to back up my intuition on the license headers I am going to lean > on > > > the "lack of creativity" exception and "PMC judgement" clause in the > ASF > > > policy :) > > > > > > https://www.apache.org/legal/src-headers.html#faq-exceptions > > > > > > Andrus > > > > > > > > > > On Jun 14, 2026, at 11:53 AM, Andrus Adamchik <[email protected]> > > > wrote: > > > > > > > > I am +1. I added MCP checks to my previous checklist (and they pass). > > > Haven't tested Modeler on Windows. > > > > > > > > Noticed the Mac .dmg doesn't have the background image and our custom > > > layout. The contents of the .dmg are correct though, so this is not a > > > blocker either. (I've seen my own builds losing the layout on rare > > > occasions; never got to the bottom of it though). > > > > > > > > One of the unit tests was missing the Apache header (my fault, I > fixed > > > that already on the "past-M2" branch). I don't think this disqualifies > > the > > > release. This is an internal unit test, and is not expected to be > > > referenced or embedded by the end users in their code. Also the new .md > > > files don't have Apache headers, which I think is totally ok. > > > > > > > > Anyone has a different opinion on this? > > > > > > > > Andrus > > > > > > > > > > > >> On Jun 13, 2026, at 12:20 PM, Michael Gentry <[email protected]> > > > wrote: > > > >> > > > >> Hello everyone! > > > >> > > > >> Finally time for the 5.0 M2 release! > > > >> Thanks Nikita and Andrus for helping with my environmental issues! > > > >> Hopefully smoother in the future. (I'll have to give Windows the > > stinky > > > >> eye.) > > > >> > > > >> Release Notes: > > > >> > > > > > > https://github.com/apache/cayenne/blob/cayenne-parent-5.0-M2/RELEASE-NOTES.txt > > > >> > > > >> Maven Repo: > > > >> > > > > > > https://repository.apache.org/content/repositories/orgapachecayenne-1063/ > > > >> > > > >> Assemblies (Note the updated KEYS file there): > > > >> https://dist.apache.org/repos/dist/dev/cayenne/ > > > >> > > > >> Please evaluate the assemblies and cast your votes. > > > >> > > > >> Thanks, > > > >> mrg > > > > > > > > > > > > > > -- > > Best regards, > > Nikita Timofeev > > >
