FpML Issues Tracker

318: Consistent tagging convention

February 21, 2007

closed

Major

Always

Schema

apparry

iyermakova

Summary

Please adopt a simple, consistent tagging convention, that states version, status, and revision within a status

The most recent tag appears to be

FpML43WD1-wd-fpml-4-3-2007-02-05

this should just simply be tagged

FpML-4-3-WD-1

following the suggested convention

FpML-major-minor-status-revision

Notes:

  • mgratacos

    03/06/07 5:04 pm

    I’d suggest incorporating the build number within the convention if available:

    FpML-major-minor-build-status-revision

    The most recent tag appears to be

    FpML43WD1-wd-fpml-4-3-2007-02-05

    this should just simply be tagged

    FpML-4-3-1-WD-1

    When the build number is not available (versions previous to 4-2 TR-2) the simple FpML-major-minor-status-revision has been adopted.

    • Leave an update

    You must be logged in to post an update.

    Report an Issue

    The FpML Issues Tracker is designed to facilitate public interaction in the standard.

    By registering you will be able to submit corrections and comments, generate reports, and view the complete issues archive for FpML.

    Report Issue