Skip to content

How to handel to leading "v" in the PyGMT release number? #4790

Description

@yvonnefroehlich

Initial comments

Currently we use a leading "v" in the PyGMT release number. However, the sematic versioning concept does not support this, xref: https://semver.org/#is-v123-a-semantic-version.

For release 0.8.0, we decided to drop the "v" in the BibTeX entry in the README to be consistent with the CITIATION.cff file (https://github.com/GenericMappingTools/pygmt/pull/2272/changes#diff-7b3ed02bc73dc06b7db906cf97aa91dec2b2eb21f2d92bc5caa761df5bbc168f). But we still use it in the meta data for the Zenodo archive:

Image

Thus, it is included in the cititation suggested by Zenodo, e.g., https://doi.org/10.5281/zenodo.3781524:

Tian, D., Leong, W. J., Fröhlich, Y., Grund, M., Schlitzer, W., Jones, M., Toney, L., Yao, J., Tong, J.-H., Magen, Y., Materna, K., Belem, A., Newton, T., Anant, A., Ziebarth, M., Quinn, J., He, X., Uieda, L.& Wessel, P. (2026). PyGMT: A Python interface for the Generic Mapping Tools (Version v0.19.0) [Computer software]. Zenodo. https://doi.org/10.5281/zenodo.19398871

Futuremore we use the "v" in the GitHub releases and tags and the file name for the Zenodo archive as well as in the table for the Minimum Supported Versions. It's also proposed in the Maintainers Guide.

We should think about whether we want to drop the "v" completely or, if not, where (and why) we still want to use it. Also need to update the Maintainers Guide afterward correspondently.

Handling by other projects

Metadata

Metadata

Assignees

No one assigned

    Labels

    discussionsNeed more discussion before taking further actions

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions