Skip to content

Moving forward to version 3.0.0 #474

Description

@nlohmann

I kept postponing the step toward version 3.0.0 for quite some time and quite some issues have been piled up. These issues have in common that fixing them will break the public API - be it very obvious such as removing deprecated functions or changing the type of exceptions or rather subtle such as begin able to store a NaN value.

Question is: How to proceed? So far, I worked in the develop branch. As soon as I, for instance, remove deprecated functions and push to develop, this code may break existing applications. I can live with that - we still have master as a branch containing the code of the last release, yesterday's 2.1.1. Furthermore, OSS-Fuzz for instance, checks the develop branch, so it would be a bit dangerous to only work in a feature branch.

I wonder whether it would be bad style to continue working in develop. What do you think?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions