Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add a version "state" property. #80

Open
Claudenw opened this issue Apr 19, 2024 · 3 comments
Open

add a version "state" property. #80

Claudenw opened this issue Apr 19, 2024 · 3 comments
Assignees

Comments

@Claudenw
Copy link

Motivation

The current DOAP lists versions but has no indication which versions are EOL, or bug fix only, or active. For purposes of automating warnings about old dependencies such a tag would be extremely valuable.

Feature
Simply a new property with a domain of Version. I am open to discussion of range and whether or not this should be a controlled vocabulary. Personally I think that it should be a controlled vocabulary to make it easier to process the data automatically.

Alternatives
Property defined in an external vocabulary.
Property with free form text.

Additional context

@ewilderj
Copy link
Owner

This is indeed interesting. One approach would be to provide suggested vocabulary terms but be open to implementors also adding their own as appropriate. Do you have any examples where we could figure out the terms?

Possible terms that cross my mind immediately would include:

  • experimental
  • release candidate
  • stable release
  • development release
  • long term supported
  • deprecated

@Claudenw
Copy link
Author

Claudenw commented Feb 9, 2025

Does deprecated == EOL == not supported?

What is the difference between development release and experimental

@Claudenw
Copy link
Author

Claudenw commented Feb 9, 2025

The DOAP file might looks something like.

<!-- my-project-0.2.rdf, also symlinked to my-project.rdf -->
<Project xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://usefulinc.com/ns/doap#">
    <name>my-project</name>
    <!-- … -->
    <canonical-release rdf:resource="./my-project.rdf"/>
    <release>
        <Version>
            <revision>0.2</revision>
            <state>stable release</state>
        </Version>
    </release>
    <release>
        <Version>
            <revision>master</revision>
            <other-release rdf:resource="./my-project-next.rdf"/>
            <state>development release</state>
        </Version>
    </release>
    <release>
        <Version>
            <revision>0.1</revision>
            <other-release rdf:resource="./my-project-0.1.rdf"/>
            <state>EOL</state>
        </Version>
    </release>
</Project>

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

No branches or pull requests

3 participants