Repository: vispy/vispy

Issue:
Bump VisPy version?
Should we bump the version to 0.4.0-dev or something? Currently it is 0.3.0, which doesn't seem right.



Discussion:
Yeah, it should be bumped, +1 for 0.4.0.dev. I prefer .dev to -dev to be
compliant with PEP440:

https://www.python.org/dev/peps/pep-0440/#public-version-identifiers

Eric

On Wed, Dec 31, 2014 at 6:21 AM, Cyrille Rossant notifications@github.com
wrote:

> Should we bump the version to 0.4.0-dev or something? Currently it is
> 0.3.0, which doesn't seem right.
> 
> —
> Reply to this email directly or view it on GitHub
> https://github.com/vispy/vispy/issues/688.

I think that should be `0.3.0.dev`?

We already released 0.3.0, so I think the .dev should be appended to the
next intended release, either 0.3.1.dev or 0.4.0.dev, whichever we are
aiming for. At least I thought the dev label went on the next intended
version, and not the last released version...

Eric

On Fri, Jan 2, 2015 at 2:15 PM, Almar Klein notifications@github.com
wrote:

> I think that should be 0.3.0.dev?
> 
> —
> Reply to this email directly or view it on GitHub
> https://github.com/vispy/vispy/issues/688#issuecomment-68567751.

I suppose we should test whether `3.0.dev > 3.0` or `4.0.dev < 4.0` with whatever function is intended for this. In string comparisons it's certainly the first... 

@Eric89GXL you're right, the standard practice is to use the next planned version and to append `dev`. So it should be either `0.3.1.dev` or `0.4.0.dev` (or idem with a hypen if we want to stick to http://semver.org/ instead of PEP440). So the question is whether we want to make a maintenance release soon or not. Have there been significant improvements since 0.3.0? I believe the scene graph is faster? Also there's the experimental WebGL backend...

String comparison is not a valid way of comparing version numbers. For example:

```
>>> '2.0'<'10.0'
False
```

I know, but people do it. It's why many packages move from e.g. `3.9` to `4.0` even when it's not a real major version bumb.

It's not our fault if people do stupid things. :)
I see no reason not to use the standard convention in the computer science world.

No, I agree. Let's used what's most common. I was not aware that `0.3.dev` was considered `< 0.3`.

My vote is for 0.4.dev, shooting for a release after the sprint, but
Cyrille if you're enthusiastic about a 3.1 maintenance release before then
I'm fine with that.

Eric

On Sat, Jan 3, 2015 at 2:28 AM, Almar Klein notifications@github.com
wrote:

> No, I agree. Let's used what's most common. I was not aware that 0.3.dev
> was considered < 0.3.
> 
> —
> Reply to this email directly or view it on GitHub
> https://github.com/vispy/vispy/issues/688#issuecomment-68590202.

@Eric89GXL If someone else wants a 0.3.1 release, let's do it, otherwise let's forget it. :)

In the future I think it might be good to make a couple of maintenance releases between two big releases.


Resolving patch:
diff --git a/vispy/__init__.py b/vispy/__init__.py
--- a/vispy/__init__.py
+++ b/vispy/__init__.py
@@ -22,7 +22,7 @@
 __all__ = ['use', 'sys_info', 'set_log_level', 'test']
 
 # Definition of the version number
-version_info = 0, 3, 0, ''  # major, minor, patch, extra
+version_info = 0, 4, 0, 'dev'  # major, minor, patch, extra
 
 # Nice string for the version (mimic how IPython composes its version str)
 __version__ = '-'.join(map(str, version_info)).replace('-', '.', 2).strip('-')


Test patch: