Forgot your password?
Close
typodupeerror

Submission + - Romance and Rebellion in Software Versioning (joabj.com) 1

Submitted by joabj
joabj writes: Most software releases more or less follow the routine convention of Major.Minor.Bugfix numbering (i.e. Linux 4.2.1). This gives administrators an idea of what updates are major ones and might bring compatibility issues. As Dominic Tarr points out in his essay "Sentimental Versioning," a few projects boldly take on more whimsical schemes for versioning, such as Donald Knuth's use of successive Pi digits to enumerate new updates to TeX, or Node.js's punk-rock careening between major and minor releases. If you break convention, Tarr seems to be arguing, at least do so with panache.
This discussion was created for logged-in users only, but now has been archived. No new comments can be posted.

Romance and Rebellion in Software Versioning More

Romance and Rebellion in Software Versioning

Comments Filter:
  • Outside of open source projects which can version their code in any intelligible or unintelligible way possible, this is how software versioning works in industry:

    Engineering: "Our current version is 1.1, and we've made enough changes that we're ready to release version 1.2."

    Marketing: "Do you think we could call it version 2.0?"

    Engineering: "Well, we added some bug fixes, and a couple of minor features, so 1.2 makes more sense."

    Marketing: "Yeah, but we think that version 2.0 sounds a lot better

Slashdot Top Deals

Regardless of whether a mission expands or contracts, administrative overhead continues to grow at a steady rate.

Close