Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
  • O osinfo-db
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 34
    • Issues 34
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 8
    • Merge requests 8
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

GitLab 15.0 has launched! Please visit Breaking changes in 15.0 and 15.0 Removals to see which breaking changes may impact your workflow.

  • libosinfo
  • osinfo-db
  • Merge requests
  • !27

Add script to generate XML for Endless OS, and add 3.6.2

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Will Thompson requested to merge wjt/osinfo-db:7-generate-endless-os-xml into master Aug 23, 2019
  • Overview 9
  • Commits 7
  • Changes 16

Closes #7 (closed). I based the template on the existing eos-3.4.xml.in file.

I have some questions:

  1. Are <upgrades> and <derives-from> mandatory? This would imply that I should also generate XML for eos-3.0 through eos-3.5 – I guess that's easy enough to implement.
  2. We (mostly) follow a tick-tock-tock-tock-tock-tock release pattern where every 6 months we release a new 3.X.0 major version, and then we make a point release in each intervening month. Our point releases are not strictly bugfixes as is common in other distros, though the major releases do contain more dramatic changes (eg new GNOME versions). I've followed the example used for (eg) Fedora and generated eos-3.6.xml.in, and we'd send another MR to update it in 2½ weeks when we release 3.6.3. Is that OK?
  3. Right now, in Boxes, there is no logo for Endless OS in the Download an OS → Show More… list. Is that some missing metadata here? Or do we need to submit our logo to some other repo?
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: 7-generate-endless-os-xml