Hello Bram,
Excerpt from Bram Moolenaar: -- <snip> -- > Including patches for runtime files doesn't take much of my time, under > the condition that I can include them as-is. Most time goes into > reviewing the change and making sure it doesn't break anything. Or > omits another change that was submitted before. > > So, what we need is a few people who can review patches. And a > procedure that is easy to use for everybody. Especially for > maintainers, so that we make their life easier and get more volunteers > that know a specific language. > > It's possible to have a repository that has the "beta-test" version of > the runtime scripts. With a small group of committers. Ideally these > people also have some scripts to check for obvious problems, such as > using line continuation without setting 'cpo'. > > I can then pull files from that repository once tested and add them to > the release repository. The group of committers could send me a list of > files to pull weekly (or whenever something important was fixed). Does > that sound like a good solution? To me absolutely yes. Obviously we will need to discuss and decide some more details/workflows but i think the consensus is broad enough to start getting it productive. Are you fine with using vim-dev as our mailinglist for all runtime related questions? > The main repository would continue to have few commits that contain a > bunch of runtime file changes. Someone interested in the details would > have to go to the "beta-test" repository. > -- Regards, Thilo 4096R/0xC70B1A8F 721B 1BA0 095C 1ABA 3FC6 7C18 89A4 A2A0 C70B 1A8F -- 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
