Release 0.5?

[astrofrog]

@ChrisBeaumont - I think it would be good to have a new release since there are already a number of improvements since 0.4 (in particular full Python 3 support). Would you object to having a 0.5 release soon? I'd be happy to help with that - if you would like me to do it, just let me know if there is a specific workflow you have been following to carry out a release.

By the way, looks like glueviz is now in the main conda package list now :)

[ChrisBeaumont]

By the way, looks like glueviz is now in the main conda package list now :)

Cool!

A 0.5 release sounds good to me. I can spend some time on bugfixes / documentation if need be. What do you think are the biggest todo items before releasing?

[astrofrog]

@ChrisBeaumont - actually I think that the only thing to be sure of is that there are no critical bugs. and that we do any kind of API change we know might happen (so e.g. what we were discussing for categorical data access). In general I'd be up for moving to a more frequent release schedule when we know there are no outstanding major issues that weren't already present before.

I'll take a look through the issue tracker and see if there are any critical things we need to do.

[astrofrog]

@ChrisBeaumont - I'd like to go ahead and do a release at the weekend, if you have no objections? Are there any special instructions for releasing? (If not, I'll do what I normally do for astropy packages). I presume that I should push to the stable branch once it's released?

[astrofrog]

The one thing I think should be added just before releasing is a 'what's new' page aimed at users. I can work on that while traveling.

[ChrisBeaumont]

I took a look over the open PRs -- it would be nice to merge #601, #656, #653 if possible, since they all look nearly-ready and add/fix cool functionality. cc @JudoWill @astrofrog thoughts?

Previous releases have been pretty standard -- push to pypi, update the stable branch, make sure that the 0.5 version of the docs is generated/posted, make sure the mac app is working

A what's new page is a good idea

[JudoWill]

#601 and #653 are about an afternoon away from being finished. I'll get them done this week.

I've also been coming up with some documentation on how to write plugins to add functionality. I'll make another PR this week. Since its primarly doc-changes it doesn't need to hold up anything.

[astrofrog]

@JudoWill - thanks! Regarding plugins, just a heads-up that I've been writing a section on writing fully custom Qt plugins here: #619 - just thought I'd let you know in case there is some overlap.

[JudoWill]

#601 and #653 are passing and ready to merge in.

[astrofrog]

@JudoWill - thanks! There are a couple of small things to fix in #601 and #653 to get Travis pass (I commented there) - could you look into these?

[astrofrog]

Once #669 is merged I will release 0.5.

[astrofrog]

I'll also hold back from actually announcing it until the package is updated in conda and I've had a chance to test it out. Since the documentation tracks the stable branch we can still push documentation updates after the release to that branch if we like.

[astrofrog]

@ChrisBeaumont - I've tagged 0.5.0, uploaded to PyPI, pushed the v0.5.0 version to the stable branch for the docs, and notified the continuum folk about the update, Python 2.6 and 3 support, and updating dependencies. I think we should wait until the package is in conda before announcing this.

@JudoWill - I think you had some doc changes you still wanted to make. Note that we can still include these on a short timescale - I'm planning on trying to increase the frequency of releases, and we can certainly have a 0.5.1 release with documentation improvements and bug fixes relatively soon.

[astrofrog]

I'm going to have to release 0.5.1 over the weekend since I found two reasonably annoying bugs (#687 and #686)

[astrofrog]

@ChrisBeaumont - just for info, now that #687, #686 and #688 have been merged, I'm going to release 0.5.1 before advertising the release.

[astrofrog]

After this is done, I'll create a v0.5.x branch (akin to what we do in Astropy) so we can maintain a bug fix branch.

[astrofrog]

0.5.1 has been released. 0.5.0 is now in conda, but there are still dependency issues, and I'm in touch with continuum about this.