Bump to 3.0.0-0.dev

[yuvipanda]

We're already on JupyterHub 4.x, so this
makes sense from a semver perspective. Useful
in generating better versions in https://hub.jupyter.org/helm-chart/.

Credit to @pnasrat for pointing this out.

[yuvipanda]

Even if we are not on JupyterHub 4.x, bumping to next version.dev after each release makes sense, and we do that for our other projects.

[consideRatio]

I think the test failures are intermittent, I'll re-run the tests later!

[consideRatio]

I figure the pattern should be to bump baseVersion to next minor with -0.dev suffix if we have merged a new feature, or next major with -0.dev suffix if we have merged a breaking change.

[yuvipanda]

@consideRatio yep makes sense re: pattern. Should we document that someplace?

[consideRatio]

@consideRatio yep makes sense re: pattern. Should we document that someplace?

I figure it belongs as a comment in chartpress.yaml next to baseVersion and possibly someplace if read by maintainers who merges PRs. I figure its mainly something maintainers merging PRs should be aware of, maybe the contributing docs?

I figure if its documented in only one place I'd value the inline comment in chartpress.yaml the msot, and if in multiple places also in contributing docs.

UPDATE: Added c0d0b3b to document this as an inline comment in chartpress.yaml.

[consideRatio]

Thank you @pnasrat and @yuvipanda!!