Skip to content

Update Apache Thrift DOAP metadata - #3707

Open
kpumuk wants to merge 1 commit into
apache:masterfrom
kpumuk:rb-update-doap-metadata
Open

Update Apache Thrift DOAP metadata#3707
kpumuk wants to merge 1 commit into
apache:masterfrom
kpumuk:rb-update-doap-metadata

Conversation

@kpumuk

@kpumuk kpumuk commented Aug 8, 2026

Copy link
Copy Markdown
Member

The mailing-list and download links currently published through the Apache Projects entry for Thrift resolve to 404 pages because the old DOAP values redirect to trailing-slash HTTPS URLs.

The releases section also shows only 0.2.0 even though the DOAP file contains 30 releases. Apache Projects collapses the collection-style release block to its final entry instead of preserving each version.

This update uses the canonical HTTPS project links and represents every version with a separate DOAP release element, allowing Apache Projects to publish the complete history from 0.24.0 through 0.2.0. It also includes Ruby in the programming-language list and aligns the maintainer contact indentation. These metadata corrections do not change runtime code.

Release structure rationale

The DOAP XML schema defines release as a repeatable property, with each occurrence containing exactly one Version. Apache Projects' own DOAP generator emits the same structure.

Although rdf:parseType="Collection" is valid RDF/XML syntax, it gives doap:release a single RDF-list value. That is semantically different from defining 30 doap:release relationships to 30 individual Version resources. Apache Projects does not expand that RDF list: its DOAP-to-JSON parser indexes the nested elements by tag name, so each Version replaces the previous one and only the final 0.2.0 entry survives.

Representing each version with a separate <release><Version>...</Version></release> element follows the DOAP schema, matches Apache Projects' supported input format, and produces all 30 release records without changing any release names, versions, or dates.

  • Did you create an Apache Jira ticket? (Request account here, not required for trivial changes)
  • If a ticket exists: Does your pull request title follow the pattern "THRIFT-NNNN: describe my issue"?
  • Did you squash your changes to a single commit? (not required, but preferred)
  • Did you do your best to avoid breaking changes? If one was needed, did you label the Jira ticket with "Breaking-Change"?
  • If your change does not involve any code, include [skip ci] anywhere in the commit message to free up build resources.

Copilot AI lite review requested due to automatic review settings August 8, 2026 20:21

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates Apache Thrift’s DOAP project metadata (doap.rdf) to use canonical HTTPS URLs (and non-trailing-slash paths where appropriate) so the Apache Projects directory links resolve correctly, while keeping the project’s published metadata accurate.

Changes:

  • Switched DOAP project identifiers/links from http:// to canonical https:// for the project, homepage, and PMC URLs.
  • Updated mailing list and download page URLs to the canonical non-trailing-slash forms.
  • Added Ruby to the explicit programming-language list and normalized maintainer contact indentation.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@kpumuk
kpumuk requested a review from Jens-G August 8, 2026 20:23
Co-Authored-By: OpenAI Codex (GPT-5.6) <codex@openai.com>
Copilot AI review requested due to automatic review settings August 8, 2026 20:37
@kpumuk
kpumuk force-pushed the rb-update-doap-metadata branch from 5dd1eb0 to 288f480 Compare August 8, 2026 20:37

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

Suppressed comments (1)

doap.rdf:65

  • The change from <release rdf:parseType="Collection"> to many standalone <release> elements materially changes the RDF structure for releases (RDF list vs repeated properties) and isn’t mentioned in the PR description. This could affect how downstream consumers (e.g., projects.apache.org tooling) interpret ordering or select the “latest” release. Either revert this structural change (keep the existing rdf:parseType="Collection" form) or explicitly justify it in the PR description with evidence that consumers still parse releases correctly.
    <release>
      <Version>
        <name>Apache Thrift</name>
        <created>2026-07-11</created>
        <revision>0.24.0</revision>
      </Version>
    </release>
    <release>

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants