Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: The E on August 28, 2015, 01:12:36 am
-
Hi folks! It's been a while since our last release, and so it's time to once again start the release cycle. As such, we need you (yes, you!) to bring bugs to our attention.
This will be the actual real final release to use DirectInput; After this is done, the much talked about merge of the SDL Everywhere featureset will finally happen.
-
Now that the FS2 SCP repo on GitHub (https://github.com/scp-fs2open/fs2open.github.com) has an issue tracker (https://github.com/scp-fs2open/fs2open.github.com/issues) of its own, what is the preferred issue tracker for FS2_Open?
On the other hand, I've reported an issue on Mantis here (http://scp.indiegames.us/mantis/view.php?id=3173).
-
I did some more testing and the issue Talon 1024 mentioned doesn't happen in 3.7.2 on any platform I can test so it looks like a regression since then. That bug is a definite release blocker but hopefully should be easy to fix with git bisect :p
EDIT: The bug was introduced in 27d85189eafb612e979649355d5ddf3000ea0bcd, a fix for this is being worked on.
EDIT2: Bug is fixed in master.
-
Now that the FS2 SCP repo on GitHub (https://github.com/scp-fs2open/fs2open.github.com) has an issue tracker (https://github.com/scp-fs2open/fs2open.github.com/issues) of its own, what is the preferred issue tracker for FS2_Open?
I don't think there's been any kind of official decision on when it is or is not preferable to use GitHub's issue tracker, but there's been something of a de facto division of "if somebody sees a problem in the code (and doesn't want/know how/have time to make a PR for it), make a GitHub issue; otherwise, make a Mantis issue", which seems sensible enough. In purely practical terms, we have too many issues in Mantis to make switching to a new issue tracker for everything anywhere close to "smooth".
There are pros and cons to making an issue on either system. On the one hand, GitHub issues get automatic integration in GitHub discussions (mentioning the number autocreates a link, and makes a note that a reference to that issue has been made along with a backlink on the issue itself). On the other hand, Mantis has features like the Roadmap, which let us see issues targeted for a specific release and what their status is. While there's no automatic resolving of issues like there was with SVN, it's probably possible to find a way to set one up for Git.
Given that, I'd personally recommend still using Mantis for the typical end-user.
-
Any way to easily make GitHub issue tracker sync with Mantis?
-
I noticed just now that the grid effect used in the ship and weapon selection screens isn't working properly. When the line starts to draw the grid, instead of the grid being revealed gradually, the whole thing appears immediately. The ship and weapon models seem to be OK, though.
Once I find the change that introduced this bug, I will post either a GitHub issue or a pull request.
EDIT: Here's the GitHub issue: https://github.com/scp-fs2open/fs2open.github.com/issues/347 (https://github.com/scp-fs2open/fs2open.github.com/issues/347)