new 0.13.0 release

[orbeckst]

Omnibus issue to discuss 0.13.0 release

Using Milestone to track Issues to include

[richardjgowers]

I think we've got enough as is, so I could do this in a few days. Then PCA
and new xdrlib becomes 0.14 with deprecations for the new system (maybe
with some compatible fixes from the new system). Then the new system is
0.15. Thoughts?

On Mon, 28 Dec 2015 20:20 Oliver Beckstein notifications@github.com wrote:

Omnibus issue to discuss 0130 release

• deprecations: Deprecations on all components to disappear or change in Topology Refactor #599
  Deprecations on all components to disappear or change in Topology Refactor #599

Please add as appropriate

—
Reply to this email directly or view it on GitHub
#600.

[orbeckst]

Getting the deprecations #599 in would be good — the sooner the better.
We'll need to go through the list of open issues for 0.13 and check which ones we deem essential and which ones can be retargeted to 0.14.

[dotsdl]

It's up to you @richardjgowers. The deprecations might take more time since we aren't completely finished with issue-363, so we don't absolutely know everything we plan to lose. Then again, we can always deprecate the things we already know are gone, such as all the setters, this release so users have more time to adapt.

[kain88-de]

Are there already alternatives in place for the stuff you want to deprecate?

[orbeckst]

That's a good point although as it looks at the moment, this is more going to be a heads up ("Hey, listen, this will go away in 0.14, mark it in your calendar!") than a deprecation because there won't be an alternative, at least as far as I understand it.

On that note, how unhappy will users be with the changes #599 related to #363 ?

[richardjgowers]

https://github.com/MDAnalysis/mdanalysis/wiki/Issue363-Changes

I started a wiki page for changes, with maybe what is going to be the largest annoyance to people.

[kain88-de]

So my stand on deprecation warnings. Only activate them when an alternative is in place and name the alternative in the warning. Otherwise I would configure my ipython rc to ignore all warnings from MDAnalysis (and forget about it by the next releases and then wonder why stuff just stopped working)

[orbeckst]

Fair enough, @kain88-de. From the wiki page on the Issue 363 changes and the discussion at #411 I don't get yet which breaks can be done with a transition phase and which ones will be a second big API break. @richardjgowers and @dotsdl will have to chime in.

[kain88-de]

Besides the questions about deprecation's I would also say we have enough for a new release. I'm sure people will be happy about the performance improvements.

[kain88-de]

Btw should we add the conda build for this release?

[richardjgowers]

I'd like to add a conda build, we've got a recipe in #571.

I could do a release in a couple of days, and we could put the deprecations in with 0.14 a month later, then 0.15.0 is mainly just the Topology overhaul on its own. Most of the fundamental code is done for the Topology, but I want to spend a while writing tests to make sure everything is 1,000% working.

[orbeckst]

The discussion on deprecations #599 indicates that we really need more time to figure that one out. Let's not bother with deprecations for 0.13.0. We can always do a 0.13.1 for deprecation messages. I'd rather get out a new release — we have a ton of important stuff and I'd rather release early and often than to keep sitting on improvements for a year.

I'd like to focus on which smaller issues really should be addressed ASAP to make it into 0.13. I added conda build to the list but I'd like folks to go through the 0.13 milestone issues. Feel free to add more checkboxes to the top issue if you want to highlight something in particular.