On Aug 3, 2010, at 9:23 AM, björn wrote: > Hi Howard, > > On 3 August 2010 08:17, H.P. Logsdon wrote: >> >> I haven't yet found any major debilitating bugs, but sure hope I can track >> some down so the RCs will be flawless. Though, I have found some things I'd >> like to submit, such as the .app bundle version identifier does not yet >> reflect the version change in its Info.plist. Curious if you want to start >> to use the GitHub page to track the 7.3 beta branch, or do you still want to >> use the Google Code page to track the issues? Have you yet worked that out? > > I must say that I'm not overly fond of issue trackers. The > possibility for anybody to add new issues means I have to constantly > prune it to keep it nice and clean (the google code one is a mess at > this moment), and often it is hard to tell if somebody has come up > with a real issue resulting in them get littered with open issues that > may never close. Also, people tend to abuse the issue list and ask > questions or mistakenly report bugs that actually aren't (and often > are covered by the vim help). In the end it adds extra work for me > and not much good seems to come out of it. > > I prefer if issue reports/feature requests/patch submissions are made > to this list so that other people may respond to them and in the > process taking some of the load off me. That being said, if somebody > has something favorable to say of issue trackers (and the GitHub one > in particular) I may be convinced to start using them in earnest. > Maybe I am just not using the "correctly"? > > So what was the problem with the Info.plist you mentioned? >
Like I said, nothing major here. It shows the version as 7.2, instead of 7.3c BETA. I only noticed that, and then became curious as to where you preferred to receive issue and bug notifications. -- You received this message from the "vim_mac" 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
