On Mon, May 31, 2021 at 6:02 PM Bram Moolenaar <[email protected]> wrote:
> Felipe Contreras wrote:
>
> > On Monday, May 31, 2021 at 11:50:10 AM UTC-5 Bram Moolenaar wrote:
> >
> > > The work on Vim 9 is making progress. Most of the syntax has settled
> > > down, but there are still a few todo items and we need to make sure
> > > everything works well before we can launch it. You can read more about
> > > it in the Vim9 help:
> > > https://github.com/vim/vim/blob/master/runtime/doc/vim9.txt
> > >
> > > It's hard to plan this, best I can say is that it still takes a few
> > > months. Once we release it we want to stay backwards compatible again,
> > > so as not to break your Vim 9 plugins. We better make sure we get it
> > > right, rather than rushing it out.
> >
> > Have you considered making a release candidate?
>
> There is a release candidate every day on github.

That's a misnomer. A release candidate is a candidate ready to be
released right now.

https://en.wikipedia.org/wiki/Software_release_life_cycle#Release_candidate

You are supposed to have 3 release candidates at most. If you have
1000 release candidates, then you have no release candidates.

If everything is important, then nothing is.

> > If you don't there's a good chance useful suggestions will come too late.
>
> That's always a problem with "releases", people just wait until the
> final release before trying it out.  Every submitted change is a
> release, in a way.

And that's why release candidates help; it's the final warning before
the actual release.

It's signaling to the users (vim developers), try it now, or else...
And they do.

The Linux and Git projects do about 2 to 3 release candidates before
any release, and that's where most issues pop up.

Git v2.32-rc0 was released two weeks ago, many users gave it a try,
they reported issues that are still being ironed out. That's 2 months
of development from v2.31.0 to v2.32.0-rc2.

I would hope after 4.7 years of development from Vim 8 to Vim 9, users
would have more than a 23-hours notice between the last "release
candidate", and the final release, which is what they had between
v7.4.2367 and v8.0.0000.

I for one don't see any particular reason to try v8.2.2912 any more
than v8.2.2186 or v8.2.$((RANDOM % 3000)) for that matter. v9.0-rc1 on
the other hand...

Cheers.

-- 
Felipe Contreras

-- 
-- 
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/CAMP44s19GvD0hFfkaUw0XiVVwjaYr0_b8PoU3uZ%3DDm5sCbRW7A%40mail.gmail.com.

Raspunde prin e-mail lui