Release 1.6 / Release Management

[ejgallego]

This issue is to discuss release management @whitequark @gasche . A few question:

• should we do a 1.6 release with the Dune-ization of ppx_import?
• should we use Github milestones to track the next release?
• where to document the release procedure using dune-release?

[gasche]

• Yes.
• I don't care, I'll follow along if you use them. The process I've been following personally is less structured: there are no planned features for ppx_import that I know of, and we can release whenever we feel that a change (from maintainers or external contributors) deserves to get in the hand of users at this point.
• as far as I know, there is currently no documentation, so if you write one you can decide where you think it is best. In some of my projects I have used a howto directory with a release file (for ocamlbuild, howto/release.adoc). Having it as part of CONTRIBUTING, or a howto-release file at the root, also seem fine for example, and I'm sure your suggestions would also be fine.

[gasche]

@ejgallego ping, are still you planning to release 1.6?

[ejgallego]

Hi @gasche indeed it is on my TODO list, but I didn't raise the priority too much as the current OPAM version is essentially 1.6.

I'd like to document the dune-release workflow better, not only for this project, but for others that I've ported to it.

[ejgallego]

Is there any rush / deadline so we should hurry up?

[gasche]

None, I was just checking/wondering -- actually I came back to this issue because I was indeed wondering about your recommended dune-release workflow. Thanks!

[ejgallego]

Sorry for the delay, hopefully I can get to this soon.

[ejgallego]

Once #31 is accepted, we can release 1.6

[ejgallego]

Closed in https://github.com/ocaml-ppx/ppx_import/releases/tag/v1.6