Re: Version numbers during development

We need to make sure that our release scripts in "support/" and CI jobs work with this change. Quite a few of them depend on the version number. Also, I know of at least one organization that does version parsing in their build scripts. I want to make sure we don't break such orgs. So we should

Re: Version numbers during development

Per offline discussion with mpark, he suggested a preference for "-dev" rather than "-devel", which sounds fine to me. Based on the lack of objections, I'll plan on making this change shortly: (1) changing the version number in master to "1.4.0-dev", and (2) updating the release process

Re: Version numbers during development

In my experience, this is reasonably common. For example, Postgres uses version numbers like "9.5devel" to identify the software in the development period before the next release process starts. Neil On Fri, May 5, 2017 at 4:23 PM, Vinod Kone wrote: > Is this a common

Re: Version numbers during development

+1 Sent from my iPhone > On May 5, 2017, at 12:56 PM, Neil Conway wrote: > > Our current practice is that when we create a branch for version X, we > bump the version number in the "master" branch to X+1. For example, we > just created the 1.3.x branch, and bumped the

Version numbers during development

Our current practice is that when we create a branch for version X, we bump the version number in the "master" branch to X+1. For example, we just created the 1.3.x branch, and bumped the version number in master to "1.4.0". Proposal: we should instead use a version number like "1.4.0-devel" in