Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add specification of release target

Open
  • Is something wrong?
#131 8 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
api, documentation

Research direction

Start with the meeting-note proposal in the issue and review the referenced PURL qualifiers and CycloneDX platform list. Done means the release-target specification has an agreed definition for the optional classifier, architecture, and package type, including the relationship to those references.

Written by the indexing model from the issue text.

Description

Prio 2 TEA Release

From meeting notes:


- __Classifier__: A reference to architecture and distro type (optional)
	ARM64/RPM - can we steal from PURL? “Qualifiers from PURL”
	CycloneDX has a list of platforms!!! <= Steal it!
	{
		“Architecture”: “ARM64”,
		“Packagetype”: “WinInstall” | “RPM” | “source” <= Package type in PURL??
	}
Dominant language
Shell
Stars
120
Forks
24
Avg merge
1d 6h
Merged PRs (30d)
67

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CycloneDX/transparency-exchange-api

All issues in CycloneDX/transparency-exchange-api

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.