Strategy for versioning on a public repo
Suppose I’m developing a (javascript) library which is hosted on a public repo (e.g. github). My aim in terms of how version numbers are assigned and incremented is to follow the guidelines of semantic versioning.
Storing revisions of a document
This is a follow up question to my original question. I’m thinking of going with generating diffs and storing those diffs in the database ‘History’ table.
Looking for best practice for version numbering of dependent software components
We are trying to decide on a good way to do version numbering for software components, which are depending on each other.
Keeping tech support on the latest software version
I’m the only software developer maintaining a subset of products at a small company. The main product I’m concerned with here is a web app which is installed on various clients’ machines, with a database and background processes.
How to start a new major version of my application, but still keep the old version ‘alive’
I have two applications, called A and B. The current version of these applciations are 7.x (some customers run 7.1, others run 7.2, …). Both applications use a same common framework (let’s call this C), like this:
Summary of differences between Java versions? [closed]
Closed. This question needs to be more focused. It is not currently accepting answers. Closed 6 years ago. This question’s answers are a community effort. Edit existing answers to improve this post. It is not currently accepting new answers or interactions. What are the major differences in between Java version in terms of software development? […]
Should semantic breaking changes be tied to syntactic breaking changes?
Explanation
Why are the version / build numbers different for Mylyn?
At projects.eclipse.org Mylyn Build 1.1.0 is slated for June 2013.
At www.eclipse.org/mylyn The “news” says Mylyn 3.8.3 was released on March 1st.
Organizing related projects and dependencies for nuget publishing
I’ve been working on writing .NET bindings for Rollbar, an error and message reporting service, like Airbrake. My library is working nicely and is published in the NuGet gallery.
Continuous Integration with Bamboo and Maven, Managing Version Numbers?
I am currently developing a product that is broken up into a few main parts: A Server, an Android client, a Desktop client, and a class library for providing common data structures. Currently my team is using Maven (with a private Nexus repo) and TeamCity to do continuous integration, but we’re having a ton of problems with builds failing due to version numbering issues. Our current solution involves using the Auto-Increment Versions Plugin for Maven, but any time we make any changes to our pom files we have to manually update the version of the pom file since the version of the pom in Git is now out of date.