Skip to content
This repository has been archived by the owner on Feb 28, 2024. It is now read-only.

Timescale for v2 API #108

Open
DStape opened this issue Jan 23, 2018 · 2 comments
Open

Timescale for v2 API #108

DStape opened this issue Jan 23, 2018 · 2 comments

Comments

@DStape
Copy link

DStape commented Jan 23, 2018

Hi @pprindeville,

Long time no speak :)

In the "Releases" section it states that, "Master will be branching soon as v1.5.x ... [and then it] will then be released as v2.0.0 which will break ABI/API compatibility".

Do you have any ideas about when that will happen? Is there further work that must be done first? If so, I can help out with that.

Thanks,
David

@pprindeville
Copy link
Collaborator

pprindeville commented Jan 23, 2018

I think we've gotten most of the major issues with the current release put to bed, with the one exception of supporting both static and dynamic builds... Issue #98 I think.

I have a bunch of improvements ready to port to 2.0, but I guess we need to branch the project. Since the number of fixes has slowed to a trickle lately, I think cherry-picking fixes into both branches shouldn't be a concern.

We could branch master as 1.x or 1.5.x and release 2.0 out of master.

@pprindeville
Copy link
Collaborator

Okay, I just did a merge of master into v1.5.x branch so it should have all the latest fixes.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants