work with pchampin to add labels for "defer-next-version" or similar.

w3c / rdf-star-wg

RDF-star Working Group

Other

25 stars 8 forks source link

work with pchampin to add labels for "defer-next-version" or similar. #137

Open ghurlbot opened 1 day ago

ghurlbot commented 1 day ago

Opened by gkellogg via IRC channel #rdf-star on irc.w3.org

Due: 2024-11-28 (Thursday 28 November)

gkellogg commented 1 day ago

Discussed adding "class-1" through "class-4" labels, as well.

pchampin commented 5 hours ago

@rdfguy @ktk @gkellogg @afs seems to me that the ms:future-work label is a good fit for that. It is present on all of our REC-track repos.

pchampin commented 5 hours ago

@gkellogg re. class-1 through class-4 labels, two remarks:

should we name them spec:class-1, spec:class-2... for homogeneity with existing labels?
should we then deprecate some of the existing spec: labels? spec:editorial would be specialized by class-1 and class-2, spec:sutstantive by class-3 and class-4, spec:bug is essentially class-3...

afs commented 5 hours ago

@rdfguy @ktk @gkellogg @afs seems to me that the ms:future-work label is a good fit for that. It is present on all of our REC-track repos.

Ah - I missed that one.

gkellogg commented 4 hours ago

Yes, ms:future-work is a good label to use. I think that spec:editorial, and such probably have better intuitive meanings than spec:class-2. But, we probably want something that has more meaning than spec:substantive or spec:bug to better distinguish between class-3 and class-4 changes.