Join GitHub today
Fault - milestone one. (I think it had something to do with waiting to see if they ever released a 'milestone two.' ) Fast-forward to today. I was again looking at this game, noting the high ratings, and noting that the next milestone had been released. Or maybe some dunces who presumed that all VNs have 18+ versions and are mysteriously.
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upHave a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
commented Sep 19, 2017 • edited
edited
Fix segmentation fault caused by implicit declaration of function 'reallocarray'. Added patch will enable reallocarray() prototype in glibc 2.26+ on Linux systems. This fix will be included in flex 2.6.5. Affected systems: Closes issue: Signed-off-by: Marko Ratkaj marko.ratkaj@sartura.hr |
commented Sep 20, 2017
add full annotation explaining what problem the patch fixes and how please. also send the fix upstream pleaseplease |
commented Sep 20, 2017
@ratkaj basically, add the full upstream commit (with its commit message) in the patch. You can do that with Also, since the upstream commit message does not mention anything about a segfault or gcc 7.2, you need to elaborate on the fix (what it does and how it fixes the problem). Lastly, please mention that it fixes FS#1003 in your commit message (not just in the pull request message). |
tools: flex: fix segfault with glibc 2.26+force-pushed the sartura:flex_fix_segfault branch from eb080f3 to 28d6d05Sep 22, 2017
commented Sep 22, 2017
Updated pull request by adding full upstream commit and correcting my commit message. |
commented Sep 24, 2017
Thank you for the patch, it was applied. |
When you are somewhere between version 1 and version 2, what do you do to maintain your software?
The terms Patch, Hotfix, Maintenance Release, Service Pack, and others are all blurry from my point of view, with different definitions depending on who you talk to.
What do you call your incremental maintenance efforts between releases?
3 Answers
When I hear those terms this is what comes to mind:
- Patch - Publicly released update tofix a known bug/issue
- Hotfix - update to fix a veryspecific issue, not always publiclyreleased
- Maintenance Release - Incrementalupdate between service packs orsoftware versions to fix multipleoutstanding issues
- Service Pack - Large Update thatfixes many outstanding issues,normally includes all Patches,Hotfixes, Maintenance releases thatpredate the service pack
That being said that isn't how we do updates at all. We just increment the version and/or build number (which is based on the date) and just call it an 'Update'. For most software I find that easier, you can easily see that one computer is running 1.1.50 vs 1.2.25 and know which is newer.
TonyBTonyBI'd like to point to http://semver.org/ for an attempt to define version numbers in sane manner, and the definitions given there actually fit closely to how I use version numbers (or how I wish I used them :))
As for the term definitions, I find patch and hotfix very similar, except 'hotfix' is usually not broadcast if done to a service.
Maintenance Release and Service Pack fit fairly closely to the two denominations of version numbers. if you have a version number structure like X.Y.Z, Maintenance Release would be the Z, Service Pack would be the Y. I've really only heard these terms in big, corporate products, though. I'm more acquainted with the minor/mayor version terms.
Of course, every shop has their own use of the terms, and it depends on which type of user you're targeting. For end-users of MMOs, for instance, every update is a 'patch' because the user has to 'patch their client' to apply it, while for end-users of more common software, you often just have the term 'update' and 'new version' (new mayor version).
A hotfix is a fix for a specific issue which is applied while the system is still active (hot). This comes from the older terms like hotswapping and hotswitching. Yes, the term is commonly misused these days by people not involved in the industry.