Hi Michael. 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.
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. 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. Hope this helps. Tell me if you need some more info or support. On Mon, Jun 1, 2026 at 12:02 AM Michael Gentry <[email protected]> wrote: > Sadly, still broken for me. > > On Sun, May 31, 2026 at 2:40 PM Andrus Adamchik <[email protected]> > wrote: > > > This worked for me, so I deleted the tag: > > > > git push origin :cayenne-parent-5.0-M2 > > ... > > - [deleted] cayenne-parent-5.0-M2 > > > > Maybe it will work now for you, that the old tag is gone? > > > > Andrus > > > > > > > On May 31, 2026, at 2:31 PM, Michael Gentry <[email protected]> > wrote: > > > > > > This command failed on me: > > > > > > mvn release:prepare -DpreparationGoals="clean install" > > > -DautoVersionSubmodules=true > > > > > > 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: > > > > > > [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. > > > > > > Same error when I use: > > > > > > git push --delete origin cayenne-parent-5.0-M2 > > > > > > Any suggestions? Or does someone else have a smoother path to take > over? > > > > > > Thanks, > > > mrg > > > > > > 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. > > > > > > > > > On Sun, May 31, 2026 at 1:29 PM Michael Gentry <[email protected]> > > wrote: > > > > > >> Hi Andrus, I'm working on it. Trying to resolve errors. I suspect the > > >> release guide is a little bit out of date. > > >> > > >> On Sun, May 31, 2026 at 9:20 AM Andrus Adamchik <[email protected]> > > >> wrote: > > >> > > >>> Hey Mike, wanted to check how things are going with the release. > Eager > > to > > >>> start using M2 and committing more cleanup code :) > > >>> > > >>> 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. > > >>> > > >>> Andrus > > >>> > > >>>> On May 25, 2026, at 8:06 PM, Michael Gentry <[email protected]> > > >>> wrote: > > >>>> > > >>>> I should be able to start it Tuesday afternoon. > > >>>> > > >>>> On Sun, May 24, 2026 at 5:47 PM Andrus Adamchik < > [email protected]> > > >>> wrote: > > >>>> > > >>>>> I think at this point we are ready to release M2. It has a huge new > > >>> scope > > >>>>> - a complete new agentic coding stack. > > >>>>> > > >>>>> Mike, do you still have time to prepare the release? > > >>>>> > > >>>>> Thanks, > > >>>>> Andrus > > >>>>> > > >>>>>> On Apr 17, 2026, at 11:00 AM, Michael Gentry <[email protected] > > > > >>>>> wrote: > > >>>>>> > > >>>>>> Hi Nikita, > > >>>>>> > > >>>>>> 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. > > >>>>>> > > >>>>>> Thanks, > > >>>>>> mrg > > >>>>>> > > >>>>>> > > >>>>>> On Tue, Apr 14, 2026 at 8:18 AM Nikita Timofeev < > > >>>>> [email protected]> > > >>>>>> wrote: > > >>>>>> > > >>>>>>> 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. > > >>>>>>> > > >>>>>>> On Tue, Apr 14, 2026 at 2:37 AM Andrus Adamchik < > > [email protected] > > >>>> > > >>>>>>> wrote: > > >>>>>>> > > >>>>>>>>> I just filed all my taxes > > >>>>>>>> > > >>>>>>>> Congrats! Which reminds me - I am still waiting for my numbers > > from > > >>> the > > >>>>>>>> accountants :) > > >>>>>>>> > > >>>>>>>>> so I have some free cycles now if there is > > >>>>>>>>> anything I can do to help. > > >>>>>>>> > > >>>>>>>> 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 ? > > >>>>>>>> > > >>>>>>>> Andrus > > >>>>>>>> > > >>>>>>>>> On Apr 13, 2026, at 6:16 PM, Michael Gentry < > [email protected] > > > > > >>>>>>> wrote: > > >>>>>>>>> > > >>>>>>>>> I just filed all my taxes, so I have some free cycles now if > > there > > >>> is > > >>>>>>>>> anything I can do to help. > > >>>>>>>>> > > >>>>>>>>> On Mon, Apr 13, 2026 at 5:08 PM Andrus Adamchik < > > >>> [email protected]> > > >>>>>>>> wrote: > > >>>>>>>>> > > >>>>>>>>>> Not too many significant new features in M2 so far, though > > quite a > > >>>>> few > > >>>>>>>> bug > > >>>>>>>>>> fixes. So yeah, we probably should do it. > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>>>>> On Apr 13, 2026, at 4:45 PM, Michael Gentry < > > [email protected] > > >>>> > > >>>>>>>> wrote: > > >>>>>>>>>>> > > >>>>>>>>>>> Is it time for a 5.0.M2? > > >>>>>>>>>>> > > >>>>>>>>>>> I noticed the M1 was released 2024-09-09 and that seems a > long > > >>> time > > >>>>>>>>>> ago... > > >>>>>>>>>>> > > >>>>>>>>>>> Thanks, > > >>>>>>>>>>> mrg > > >>>>>>>>>> > > >>>>>>>>>> > > >>>>>>>> > > >>>>>>>> > > >>>>>>> > > >>>>>>> -- > > >>>>>>> Best regards, > > >>>>>>> Nikita Timofeev > > >>>>>>> > > >>>>> > > >>>>> > > >>> > > >>> > > > > > -- Best regards, Nikita Timofeev
