Patches for `1.x.y`

[dcousens]

Just curious how did we want to handle bug fixes and patches for 1.x.y after we release the 2.0.0 tag?

I have set up a 1.5.x branch for now which I'll rebase some fixes on to, but naturally I don't want to spending all my time back-porting changes.

@weilu ?

[dcousens]

This has come to light after the merge of #317 (backwards incompatible) and opening of #372 (based on the now backwards incompatible master)

[weilu]

I have set up a 1.5.x branch for now which I'll rebase some fixes on to

That's the way I'd suggest

but naturally I don't want to spending all my time back-porting changes.

Agreed. How about we set an end-of-life for 1.x.x? say 3 months after 2.0.0 comes out?

[dcousens]

@weilu I think that is fair, but that could become harder as time goes on and the internals change.

[dcousens]

Currently being tracked by #376, will close this.