KhronosGroup / KhronosGroup/OpenCL-Docs

tagging convention for OpenCL ecosystem repos

Open
#539 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
420
Forks
131
Avg merge
5d 13h
Merged PRs (30d)
11

Description

This issue is a follow-up from the December 2020 maintenance release: https://github.com/KhronosGroup/OpenCL-Docs/issues/528.

Many of the OpenCL repos use a date-based tagging scheme but the spec and the C++ bindings use a version-based tagging scheme. Should we adopt a consistent tagging scheme for all of the OpenCL repos? If so, which tagging scheme should we adopt?

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the linked follow-up issue, OpenCL-Docs#528, and comparing the date-based and version-based tags used across the OpenCL repositories. Done means the ecosystem has an agreed tagging scheme and a documented decision about which convention to adopt.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, github
Domain
release
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.