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. -- -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/ZUDVRa0JU7L/6Avu%40256bit.org.
