Yes. But we may have messed up the announcement. 

> On Apr 11, 2025, at 5:19 PM, Michael Gentry <blackn...@gmail.com> wrote:
> 
> Hi Nikita,
> 
> Did this ever get officially released/published?
> 
> Thanks,
> mrg
> 
> 
> On Fri, Mar 21, 2025 at 4:46 PM Nikita Timofeev <ntimof...@objectstyle.com>
> wrote:
> 
>> Here's a final voting result:
>> 
>> Michael Gentry (PMC) +1
>> Andrus Adamchik (PMC): +1
>> Nikita Timofeev (PMC): +1
>> 
>> With additional checks from Jurgen Doll and Hugo Thordarson.
>> 
>> Thank you everyone!
>> I'll finish this release shortly.
>> 
>> On Thu, Mar 20, 2025 at 10:10 AM Hugi Thordarson <h...@karlmenn.is> wrote:
>> 
>>> Second that :)
>>> 
>>> - hugi
>>> 
>>> 
>>> 
>>>> On 19 Mar 2025, at 20:38, Jurgen Doll <jur...@ivoryemr.co.za> wrote:
>>>> 
>>>> +1 from Jurgen, issue has been addressed - thanks.
>>>> 
>>>> On Mar 19 2025, at 8:22 pm, Andrus Adamchik <aadamc...@gmail.com>
>> wrote:
>>>>> I am +1
>>>>> 
>>>>> Though would be nice if Jurgen (and Hugi) could confirm the problem we
>>> had during the original vote is addressed.
>>>>> Also, I am mindful of another Hugi's email ("Cayenne v4.2: Updating a
>>> related objects in @PreUpdate results in CommitLogListener receiving a
>> bad
>>> ChangeMap"), but since that's not "new", I suggest we discuss is
>> separately
>>> and let the release go through.
>>>>> Thanks,
>>>>> Andrus
>>>>> 
>>>>>> On Mar 14, 2025, at 9:42 AM, Nikita Timofeev <
>>> ntimof...@objectstyle.com> wrote:
>>>>>> 
>>>>>> Hi all,
>>>>>> 
>>>>>> Here's Cayenne 4.2.2 again, with reimplemented fix for CAY-2876
>>>>>> 
>>>>>> Release notes:
>>>>>> https://github.com/apache/cayenne/blob/4.2.2/RELEASE-NOTES.txt
>>>>>> Maven repo:
>>>>>> 
>>> 
>> https://repository.apache.org/content/repositories/orgapachecayenne-1060/
>>>>>> Assemblies:
>>> https://dist.apache.org/repos/dist/dev/cayenne/4.2.2-vote2/
>>>>>> 
>>>>>> Please evaluate and cast your votes.
>>>>>> 
>>>>>> --
>>>>>> Best regards,
>>>>>> Nikita Timofeev
>>>>> 
>>>> 
>>> 
>>> 
>> 
>> --
>> Best regards,
>> Nikita Timofeev
>> 

Reply via email to