On 11-Apr-2010 Bram Moolenaar <[email protected]> wrote: > > Christian Brabandt wrote: > > > Are you considering any patches from > > http://groups.google.com/group/vim_dev/web/vim-patches > > for inclusion? > > Yes, but many of these patches are not mature. E.g., first one, > "Improved regular expression engine", is still lacking the tests to > verify that it doesn't break anything. That's a pity, because it can > make syntax highlighting much faster. > > I want to avoid that I include something that triggers a long sequence > of bug fixes. "Works fine for me" is not always a good indication. > 7.3 is going to be a stable release, thus I don't want to take too much > risc. Part of my work will be to estimate the risc, which involves > carefully looking through the code changes.
Unfortunately, this means that some features are very unlikely to make it into Vim 7.3 (or any later version for that matter). If it's the bug fixes that worry you, then I can't think of a solution. But if you simply don't like the idea of providing the users with Vim that might be unstable, then maybe you would accept one of the solutions: - let Vim stay in 7.3-alpha stage for a longer while, - release Vim 7.3 but then create a testing branch of Vim. The main branch and the testing branch would get normal bug fixes, but the testing branch would also be the place for developing new features. Either way, I believe there are people who would be willing to accept Vim of alpha quality for the price of getting interesting features in (I for one would, perhaps the vim-dev subscribers as well). By the way, if there is any task during preparing Vim 7.3 that you think you could "outsource" ;-) I can commit myself to spending a day a week on Vim for the next month or two. -- Cheers, Lech -- 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
