On So, 27 Aug 2023, Yegappan Lakshmanan wrote:

> Hi Christian,
> 
> On Sun, Aug 27, 2023 at 11:09 AM Christian Brabandt <cbli...@256bit.org> 
> wrote:
> >
> > >
> > > On Thu, 24 Aug 2023 at 06:18, Christian Brabandt <cbli...@256bit.org> 
> > > wrote:
> > >
> > >     Hi,
> > >     this is a small update over what happened the last few weeks.
> > >
> > >     Over the last days, I have been merging mostly runtime file changes,
> > >     small improvements to the Vim9 class implementations and bug fixes.
> > >
> > >     If you check the Milestone¹ for the release 9.1, most of the remaining
> > >     changes are small runtime changes, for which I'd like to get an
> > >     ACK/NACK.
> > >
> > >
> > > Did you have a rough date in mind for the release?  Are we looking at 
> > > weeks or months?
> >
> > I did go through the Vim9.1 milestone and try to merge what seems
> > uncontroversial and fixes crashes. But somehow I keep getting new PRs
> > there all the time :) (I am joking)
> >
> 
> :-).  I keep adding the runtime file changes and minor fixes to the
> Vim 9.1 milestone.
> Can we take fixes for one more week and then stop?

Yes of course.

> 
> >
> > I would think once Yegappan thinks the Vim9 classes is good enough to
> > release, I'd go ahead. Not sure how much work this is left to be done,
> >
> 
> I want to make sure that all the Vim9 class changes that may break backward
> compatibility go in before the Vim 9.1 release.  I think, we are down to the
> last one and it is about the default access for an object/class member 
> variable.

Perfect. That is fine.

Best,
Christian
-- 
18th Rule of Friendship:
        A friend will let you hold the ladder while he goes up on the roof
        to install your new aerial, which is the biggest son-of-a-bitch you
        ever saw.
                -- Esquire, May 1977

-- 
-- 
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/ZOxK4EdP0IV8idP3%40256bit.org.

Raspunde prin e-mail lui