Thanks Mike!
> On Jul 4, 2026, at 10:27 AM, Michael Gentry <[email protected]> wrote:
>
> To answer my own question about publishing, I found the "mvn publish"
> command. Web site is now updated.
>
> On Fri, Jul 3, 2026 at 2:21 PM Michael Gentry <[email protected]> wrote:
>
>> The new tag worked. I committed my changes. Let me know if I need to
>> change anything.
>>
>> Does the site auto-publish or do I need to do something?
>>
>> Do I need to email the Apache announce list?
>>
>> I'll try to do the Twitter and BSKY messages now.
>>
>>
>> On Fri, Jul 3, 2026 at 10:07 AM Andrus Adamchik <[email protected]>
>> wrote:
>>
>>>
>>>
>>>> On Jul 3, 2026, at 7:50 AM, Michael Gentry <[email protected]> wrote:
>>>>
>>>> When I navigate to http://localhost:3000/download/ the top of the page
>>> is
>>>> the 5.0-M2 release as expected, but the release notes link goes to
>>>> https://github.com/apache/cayenne/blob/5.0-M2/RELEASE-NOTES.txt which
>>> is
>>>> incorrect. It should go to
>>>>
>>> https://github.com/apache/cayenne/blob/cayenne-parent-5.0-M2/RELEASE-NOTES.txt
>>> .
>>>> Think link works for M1.
>>>
>>> Yeah, this is related to how the tag was named. Nothing wrong with the
>>> "cayenne-parent-5.0-M2" name per se, but it is not compatible with the site
>>> assembly template. So I just manually pushed a "5.0-M2" tag pointing to the
>>> same commit and the "canonical" link now works.
>>>
>>>
>>>> Also, the "Cayenne 5.0-M2 source code distribution" link is
>>> semi-broken. To
>>>> be fair, it is the same for other releases, too. The M1 link points to
>>>>
>>> https://www.apache.org/dyn/closer.cgi/cayenne/5.0-M1/cayenne-5.0-M1-src.tar.gz
>>>> for example. Or is that the expectation?
>>>
>>> Not sure about this one.
>>>
>>> Andrus
>>>
>>>
