Ok, I've added the message. (In order to do this I had to reopen all issues and then close them again.)
On Thu, Oct 17, 2024 at 8:45 AM Julian Hyde <jhyde.apa...@gmail.com> wrote: > > Thank you - but it doesn’t look like you added the message 'Resolved in > release 1.38.0 (2024-10-15)’ per the release instructions. > > > > On Oct 17, 2024, at 3:22 AM, Xiong Duan <xi...@apache.org> wrote: > > > > I have marked all Jira cases in 1.38 closed. > > > > Julian Hyde <jhyde.apa...@gmail.com> 于2024年10月17日周四 15:20写道： > >> > >> I still need to mark all jira cases in 1.38 closed. Sorry I haven’t had > >> time. I’ll get to it today. > >> > >> Julian > >> > >>> On Oct 16, 2024, at 18:29, Xiong Duan <xi...@apache.org> wrote: > >>> > >>> The Jira issue status is RESOLVED at about 1.38, it should be CLOSED. > >>> So I update it. > >>> > >>> Alessandro Solimando <alessandro.solima...@gmail.com> 于2024年10月16日周三 > >>> 16:07写道： > >>>> > >>>> Thanks Francis! > >>>> > >>>>> On Wed, 16 Oct 2024 at 10:02, Francis Chuang <francischu...@apache.org> > >>>>> wrote: > >>>>> > >>>>> I've marked it as released. > >>>>> > >>>>> On 16/10/2024 6:58 pm, Alessandro Solimando wrote: > >>>>>> Hello, > >>>>>> first of all thanks to Julian for being the RM of 1.38.0 and to > >>>>>> everyone > >>>>>> involved. > >>>>>> > >>>>>> I noticed that 1.38.0 it's still under "unreleased" versions in Jira, > >>>>>> can > >>>>>> someone with the right permissions fix it? > >>>>>> > >>>>>> Best regards, > >>>>>> Alessandro > >>>>>> > >>>>> > >>>>> >
