BMSBugs: A public third party BMS bugtracker
-
I think with your account permissions, you need to either be assigned to the issue, or to have opened the issue, to be able to close it. It was reported by Anonymous, and Mav-JP is assigned to it.
Ill edit the reporter field to you, and also close the issue. Thanks for updating the public issues!
-
Reminder for everyone who has logged a bug: we’d love an update if your bug has been resolved by 4.35 U1 - you can mark any issues fixed, as closed, once the fix is confirmed.
Thanks for using the tracker!
-
Issue #21 and Issue #81 were both reported anonymously. This is okay, but it does leave us without a reporter who can confirm that the issue they saw has been fixed (or not) in U1.
Id appreciate anyone who is able to try out the reproduction instructions for either issue and see if the issue can still be reproduced in U1, and comment to that effect on the issue.
Thanks again.
-
Looks like I’m unable to add notes to closed issues so I replied by email to “admin@bmsbugs……” to your questions on the two bugs you sent in the comments. Hope that’s ok!
All the best,
Uwe
-
Looks like I’m unable to add notes to closed issues so I replied by email to “admin@bmsbugs……” to your questions on the two bugs you sent in the comments. Hope that’s ok!
All the best,
Uwe
Thanks for getting back to me. Ive just now amended the setting which was preventing users from responding to resolved issues.
To that effect: anyone who has been unable to respond up to now, you should be able to log in and respond on those issues at this point. Thanks for your patience while we work out the kinks in the system.
-
And we got our first bit of spam on the tracker! I may need to tighten up security a little. This may include removing the ability to post anonymously, although this isnt part of the plans just yet.
-
Hi Blu3wolf a few days ago I posted bug no 119. Do I have to make a bug report here in the forum as well?
https://bmsbugs.blu3wolf.com/view.php?id=119 -
Reporting on the tracker is appreciated, thanks! BMS Devs do view the new issues, but as you may have noticed there are quite a few other issues and the dev team are quite busy, so not all issues are commented on immediately.
This is especially the case for minor graphics glitches - there are a number of crashes still occurring in U1 and I suspect the crashes are likely a higher priority for the team.
The primary goal with the bug tracker is to document issues with the sim, so that they can be fixed - and so that people need not make multiple reports about a bug which is already known, avoiding duplication of effort. If you think your issue is likely to be due to your setup and not due to a flaw in the sim, it may be worth making a post in the technical support forum here, to ask for help from other forum members.
As your issue seems like a sim issue rather than a setup issue, the bug tracker is the right place for it, and hopefully it will be fixed in a future version of BMS. Thanks for helping document BMS’ current state.
-
I thought some folks might be interested in a short status update.
BMSBugs has seen quite a bit of activity in the last three months, quite a bit more than Id really anticipated, which is wonderful to see. We have had 142 bug reports opened, mostly in the Falcon BMS project - although there have been a few issues opened in the EMF and ITO projects, most have been either against BMS itself, or the documentation suite. A number of the issues have described long-standing issues, some of them very minor and others which are a little more significant, and many more have been new issues with 4.35.
Over a third of all the issues reported have been resolved so far, by Update 1. Im quite grateful to the BMS devs for putting in time to look at the community issues, and for taking the time to advise us of upcoming bug fixes to our reported issues. Once a developer has advised that a fix has been made for the next update, the issue is considered “resolved” but it remains “open” until that fix is released, at which point the issue is “closed”. So far, the average issue is resolved in just 9 days, which is quite responsive considering the volunteer nature of the development and the limited number of team members.
There are still 92 open issues (across all projects), and interestingly enough every category of issue has at least one issue in it! The two ‘busiest’ categories being “General” and “Avionics”, with “Campaign” and “Multiplayer” as runners up. Just under half of all issues are reported anonymously, although this is possibly unintentional as many of the issues reported anonymously end up with the reporter logging in to make comments on the issue. Around a quarter of anonymous issues are either a duplicate, or not a bug, or unable to reproduce, while most issues reported by logged in users are valid bug reports.
A fairly high proportion of issues are reported as “high priority” when they are reported, although I dont have numbers presently. A handful of bugs have been marked as high, urgent or immediate priority by devs - I was very happy to see this kind of public feedback when it happened, and hope to see it more in the future, as it builds community confidence in the BMS team. Priority settings below “normal” have mostly been set by users voluntarily, and about 81% of all issues are “normal” priority.
I am grateful to everyone who has reported an issue, commented, or provided feedback - and I am especially grateful to those who are working on fixing these issues, as well as taking the time to let us know how those fixes are going. Thank you for doing your part to help improve BMS.
-
Thanks for the information and thanks to the developers.
-
Another quick update for users of the BMSBugs tracker. We’ve had our first (edit: automated) instance of spam, which was brought to my attention a bit over 2 hours ago. This consisted of “notes”, the tracker’s equivalent of comments, being posted from the anonymous account.
The tracker was taken offline for a couple hours to avoid further spam being added while it was being rolled-back. 75 spam comments have been deleted, and the anonymous account’s permissions severely curtailed to stop further spam. The tracker is back online now, but the anonymous account is limited only to permitting users to view issues - interacting with the site in any way other than viewing will now require signup, which was previously optional.
Signup is a fairly quick process, and allows you to edit your issues later. It requires providing a valid email address for verification, which is used for email notification of updates to your issues. I had preferred to have an anonymous option for those who would prefer not to provide an email address, but this seems not viable.
The site is now back up and running, and we have even had a couple new issues reported in the time Ive been writing this post. Thanks to Echoes for pointing out the spam to me, and thanks again to everyone submitting issues to the tracker - the thing that really sets BMS apart is the community, and I’m glad every time one of you spends some of your valuable time to write a bug report.
-
-
<p>In the Login page of the Bugtracker I see the following warning:<br /><br />>>><br />Warning: “admin” directory should be removed, or access to it restricted.<br /><<<<br /><br />To which “admin” directory is this refering to ?<br />To the “admin” directory on my local PC ?<br /><br />Thanx<br />Sunnny</p>
-
@Blu3wolf is this still supported?
We have a lot of external testers today, and I would like to use your bugtracker.
-