Is there a vim9.1 release plan/requirements?

[Ernie Rael]

Greetings programs,

A vim9.1 release has vim9script and everything else. I have little sense
of what "everything else" is in this context; I have recently seen
"complete_info" and "safe executable check". Is there much that needs to
be done for vim9.1 (not considering vim9script)?

Just opened "Language Specification: vim9.1 vim9script freeze"[1] to
discuss whether or not vim9script is in a good position to freeze and
release; along with what might be needed to get there and/or polish it
up. I hope the community contributes.

Throwing a dart at the wall, I'd look for 2 weeks of cleanup/fixes and 2
weeks of freeze where only significant fixes go in with a Nov 1 release.
Assumes the current "single branch" repo model is used.

The MCP will have to contemplate, meditate, and otherwise look at the
situation and make a scheduling decisions.

[1] "Language Specification: vim9.1 vim9script freeze"
https://github.com/vim/vim/discussions/13454

-ernie

[Christian Brabandt]

On So, 29 Okt 2023, Ernie Rael wrote:

> Greetings programs,
>
> A vim9.1 release has vim9script and everything else. I have little sense of
> what "everything else" is in this context; I have recently seen
> "complete_info" and "safe executable check". Is there much that needs to be
> done for vim9.1 (not considering vim9script)?

No, that doesn't need to go to 9.1. But the complete_info fix seems
small enough and as a bug fix should qualify.

> Just opened "Language Specification: vim9.1 vim9script freeze"[1] to discuss
> whether or not vim9script is in a good position to freeze and release; along
> with what might be needed to get there and/or polish it up. I hope the
> community contributes.
>
> Throwing a dart at the wall, I'd look for 2 weeks of cleanup/fixes and 2
> weeks of freeze where only significant fixes go in with a Nov 1 release.
> Assumes the current "single branch" repo model is used.
>

You mean Dec 1? Other than that, that sound reasonable. Assuming the Vim
9 specs are considered feature complete (I trust Yegappan here), this
makes sense and I would only include clear bug fixes + runtime file
updates + security updates. However, I need to find out, what has to be
done for a 9.1 release (updating version9.txt including all patches and
consistently updating all the naming issues). I don't know how much work
that is. I guess we all have to learn something here

Thanks,
Christian
--
Today is the first day of the rest of your life.

[Ernie Rael]

On 23/10/31 3:21 AM, Christian Brabandt wrote:
> On So, 29 Okt 2023, Ernie Rael wrote:
>
>> Greetings programs,
>>
>> A vim9.1 release has vim9script and everything else. I have little sense of
>> what "everything else" is in this context; I have recently seen
>> "complete_info" and "safe executable check". Is there much that needs to be
>> done for vim9.1 (not considering vim9script)?
> No, that doesn't need to go to 9.1. But the complete_info fix seems
> small enough and as a bug fix should qualify.

Those were simply two things I recently saw. Just pointing out that
there could well be things pending that need to get into vim9.1.

>
>> Just opened "Language Specification: vim9.1 vim9script freeze"[1] to discuss
>> whether or not vim9script is in a good position to freeze and release; along
>> with what might be needed to get there and/or polish it up. I hope the
>> community contributes.
>>
>> Throwing a dart at the wall, I'd look for 2 weeks of cleanup/fixes and 2
>> weeks of freeze where only significant fixes go in with a Nov 1 release.
>> Assumes the current "single branch" repo model is used.
>>
> You mean Dec 1?

(Yikes, glad I didn't put a year in there somewhere.) Yes, for instance.