API v2 meta-issue

[yarikoptic]

I think it is time to start collecting issues which are to be addressed in a new API version, i.e. that fixing them require a breaking change likely to be done only in v2; or we do not have explicit issue and should be described here

• Fix naming of path and path_prefix parameter names #1562
• Do a comprehensive design review of the API #1228

[jwodder]

Related: #1228

[yarikoptic]

cool, thank you @jwodder -- I have added it to original description. If more to come -- just edit (I think everyone would have permissions) original description and add there

[waxlamp]

It should be v1 right? Right now we're on v0.

[yarikoptic]

Kinda. We can call it v1 but...:
I named it v2 since in effect we are having v1 as it could be the version we eventually release before v2 as to establish something "stable", although suboptimal.
It would be odd to call it v1 since for me "finally releasing v1" means more of "finally now we are giving something stable after all the 0.x releases". A new API should not have such pompous entry IMHO ;-)
In PyMVPA we similarly skipped v1 release altogether and went from 0.x to 2.0 for similar'ish reasoning.