So far we have been testing by hoping for people to install Vim and use it. This does find problems related to daily use, but I suspect quite a few things are not yet used and bugs go unnoticed. Then when Vim 7.3 is released new features get used and bugs are uncovered. Too late!
It would be good if we have someone systematically going through new features and recent changes, making a list of use cases that need to be tested. Possibly using the help as a guideline and brainstorming of situations and border cases that might have problems. Then we need to have people who take one of the uses cases and run through them. Verify that it works as expected. Try a few variants while doing that. This should not take much time. I have started a shared document for this. it's very rudimentary: https://docs.google.com/document/edit?id=1CyOvJqKYoTmL4D50w2htYMG7xt5SADcIX6r7zZ978HQ&hl=en&authkey=COfQ_6oD I need to spend my time on fixing bugs, it would be great if someone can step forward to coordinate this testing. This includes making the layout of the document better and keeping an eye on the progress. I also wonder if a shared document is the best way to do these things. At least this allows multiple people at the same time making changes. Most wiki's are not good at that. Comments? -- ARTHUR: It is I, Arthur, son of Uther Pendragon, from the castle of Camelot. King of all Britons, defeator of the Saxons, sovereign of all England! [Pause] SOLDIER: Get away! "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ download, build and distribute -- http://www.A-A-P.org /// \\\ 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
