F.A.G
F = increment it roughly every 45 days so people think the project is alive
A = number of SJWs who appreciated the "improvements" in the software this month
G = number of lines rewritten in Rust
Versioning
hahaha great post well memed my friend
For libraries semantic versioning is great, but for end-user applications it doesn't really matter I guess. I mean, Firefox is now at version 55, WTF does that even mean?
Personally I would use file or scripting compatibility as the major version in an end-user application. For example, if it's a word processor and the file format changes (even if it is backwards compatible with the old one) I would increment to major number.
You wish it was just a meme...
Oh, don't forget to check out our latest Nightly
mozilla.org
New:
- Firefox Nightly has a new logo (feels good)
- Added an option to the Page Action menu to report a website issue in Firefox Nightly and Firefox Dev Edition (feel free to report all sites with Javascripts and opposing opinions. Not too many used the "Share" button, so we replaced it with "Report" :-) )
- Firefox Nightly now gets updated twice a day so as to help our communities in EMEA and Asia regions to catch regressions and report them during the Americas night. (nice, huh?)
Now can you guess the final version numbers of the stable release which will include these?
the actual release notes:
you got fact checked. nice try trying to fake news me though.
As one of the classiest pornstars out there, he's close to being the final version of a software.
I'm a strong believer of stopping development of a software when it has served it's purpose and not continuously bloating it ad infinitum.
arbitrary versioning:
number of versions that have been incompatible with previous versions
.
major releases
.
critical bugfix patches