roadmap for next versions of BigInts (>=0.6.0) about bigints

[pietroppeter]

I fear we might be multiple people working on the same thing in the future.

I like the optimism ;)

[konsumlamm]

I noticed there is almost no information for new developer to know what the developers are currently working on. I fear we might be multiple people working on the same thing in the future.

I'm pretty sure that's just because noone is working on anything (besides the open PRs).

Another thing we should agree on and document is the versioning policy (there is no officially recommended one afaik). One possibility is using semver. We should keep in mind that some of the changes so far are technically breaking (adding new exceptions that can be raised), but that would be ok for 0.6 with semver. Also note that bigints.nimble currently says the version is 1.0.0.

cc @narimiran

[dlesnoff]

Also note that bigints.nimble currently says the version is 1.0.0.
Can we downgrade the nimble version to the last tagged one ?
Another thing we should agree on and document is the versioning policy (there is no officially recommended one afaik). One possibility is using semver.

I thought semantic versioning was the official one for nimble packages. Do you know some other versioning policies ?
I am for semver. We should be careful with the API though. To detect changes, we want to integrate the examples into the CI.
Who decide when a new release is made ? Some breaking change in the API might be reverted back by a future commit. I am thus against : a breaking change implies a new release.