fixed order of returns for inverselink(::Link01), and other compatibility fixes for GLM2

[ajinkya-k]

see #11

TODOs:

• bump version number to v0.2.0
• bump compat for GLM to GLM >= 2
• check if version bump is correct per SemVer
• compat needs work

Before testing using Pkg; Pkg.develop("/path/to/dev/v2/GLM.jl/") must be run

[ajinkya-k]

How do we modify CI for this PR so that Pkg.develop("/path/to/dev/v2/GLM") can be added?

[ararslan]

Hi @ajinkya-k, thanks for the PR (and corresponding issue)! Since GLM 2.0 hasn't been released yet, I'd prefer to keep the compatibility limited to GLM 1.x for now. We can revisit this PR once GLM 2.0 has been released.

[ajinkya-k]

That makes sense. I should have made it a draft PR, sorry

[ajinkya-k]

Can we add label/tag to mark it as "future" or "v0.2" or something?

[ararslan]

I should have made it a draft PR, sorry

No worries! It can be made into a draft after the fact.

Can we add label/tag to mark it as "future" or "v0.2" or something?

Regarding v0.2, note that the changes made to GLM don't necessarily warrant a breaking release of this package, as this package's API wouldn't change. The fact that it uses GLM internally is an implementation detail in some sense.

[ajinkya-k]

right, but we would have to bump up the compat for GLM and the patch number atleast right? because if someone uses this package at 0.1.4 with GLM2 that will break things. I am guesing it can be 0.1.x but we would need a patch release that needs a GLM update

[ararslan]

if someone uses this package at 0.1.4 with GLM2 that will break things

They wouldn't be able to do that, since this package currently declares compatibility in Project.toml as GLM = "1", so GLM 2 would not be installable alongside BetaRegression.

I am guesing it can be 0.1.x but we would need a patch release that needs a GLM update

That's right