> ### Steps to reproduce > > **Description** > > [`winget`](https://github.com/microsoft/winget-cli) is a Windows command line > package manager offering functionality similar to apt-get on Linux, or > homebrew on MacOS. > > Vim is published in the winget packages repo, **which is very nice and I do > appreciate it**. > > But it looks like what is published is a daily build, similar to what is > tagged here, in github. > (https://github.com/vim/vim/tags) > > That is way too often, to the point of being annoying. > Imagine that an `apt-get upgrade` would update your Linux `vim` every single > day. > Does anyone really need to be at the bleeding edge, every single day? > > See here the winget packages: > https://github.com/microsoft/winget-pkgs/tree/master/manifests/v/vim/vim > > --- > > **Reproducing it:** > > Using in Windows install `vim`: > ``` > winget install vim.vim > ``` > Then every day try to update it: > ``` > winget upgrade vim.vim > ``` > There will be an update almost daily. > > --- > > Are there any milestones that are more important than others? > Something reflected in the version (which seems to be semantic, in some way)? > Or every 10 / 20 / 30 builds? > If not, then maybe publish separate packages (vimdaily, vimweekly, > winmonthly?) It is very difficult to decide what would go in what package. If we automate it, e.g. make a weekly package every Wednesday, then I'm sure in some weeks it's missing some patch that was made just after it, and we might have to make an extra one. It's a lot simpler to handle this on the installer side: Just make a daily package and you decide when you'll get it. So you can get it on every Wednesday. But when something is missing, you can get next day's package. This takes away a lot of work on the distribution side. Do not underestimate how much effort goes into planning releases. It's alway a lot of discussion, and then usually an hour after the release a problem is found and the release needs to be updated. > And _"don't update that often"_ is also not as convenient. In fact it > can be dangerous. > Now one would potentially use a vulnerable app (imagine Chrome) for a > week (or more). Vim fixes serious problems very quickly, a daily update fits with that. Many "professional" apps are only updated infrequently, it may take one or two months. For Chrome, when there is something so serious it's in the news, they usually have a new version almost immediately. But the regular updates (I believe these come every six weeks) usually fix a dozen security issues. -- Kiss me twice. I'm schizophrenic. /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// \\\ \\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- -- 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/20230106121243.A1BB01C13F2%40moolenaar.net.
