On Wed, 9 Aug 2023 at 03:56, Christian Brabandt <cbli...@256bit.org> wrote:
> > On Di, 08 Aug 2023, Yegappan Lakshmanan wrote: > > > I am not suggesting a separate minor release for each runtime file > update here. > > Otherwise, we will have too many minor releases. Can we make a minor > release > > only for PRs that change the C code and not the runtime files (still > > merge the runtime changes as separate PRs)? > > Yes, that should be possible. We can merge runtime files directly, > without incrementing the minor patch number and only increment the minor > patch number for changes to the source (including diff, libvterm, xxd or > the test suite) > Runtime file updates often include test updates (e.g., filetype detection tests) and changes to runtime infrastructure (e.g., runtime/ftplugin.vim) are also arguably worth a version bump. Bram's distinction here actually makes a lot of sense but may, I understand, not be tenable. Regards, Doug -- -- 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/CAJ1uvoC5POrwToUac18EcfsBfgPa9Nu9BuF%2B955fMDXq1x8QgA%40mail.gmail.com.
