microg / microg/GmsCore

How to know whether a release is / was a stable release?

Open
#3,158 13 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

question
Dominant language
Java
Stars
14.6k
Forks
3.2k
Avg merge
12d 11h
Merged PRs (30d)
4

Description

There used to be a 'Downloads` page which listed the latest 'stable' releases of the microG components (https://microg.org/dl/ or maybe https://microg.org/download.html). That page has not been available since the July web site outage, and current download links lead either to the Downloads Wiki page https://github.com/microg/GmsCore/wiki/Downloads, or to the GitHub releases page https://github.com/microg/GmsCore/releases.

Until recently, I believe that the GitHub releases pages marked beta versions as 'pre-release` and stable versions as 'latest' but this no longer seems to be the case. And yesterday the 0.3.10 release changed from being marked as 'pre-release' to 'latest'. So 2 questions:

  1. Is 0.3.10 now regraded as Stable, rather than beta / pre-release?
  2. How can we find out whether new releases are stable or beta? (Same question applies to old releases - was a release stabe or beta - though it is less important / interesting.

Thanks

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start with the Downloads Wiki page and the GitHub releases page linked in the issue, then compare how 0.3.10 and older releases are labeled. A useful outcome would document how to identify stable versus beta releases and clarify the status of 0.3.10, including the historical case where relevant.

Written by the indexing model from the issue text.

Assessment

Tech stack
github
Domain
documentation, release
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.