Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Container image release version discrepancies #2040

Open
5 tasks done
schewara opened this issue Jul 27, 2023 · 1 comment
Open
5 tasks done

Container image release version discrepancies #2040

schewara opened this issue Jul 27, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@schewara
Copy link

Component

other

Describe the bug

While the latest release here is tagged with v1.0.0-rc1

On Docker Hub there is already a v1.0 which I would interpret as final stable 1.0 release

see -> https://hub.docker.com/r/woodpeckerci/woodpecker-server/tags?page=1&name=1.0

In addition the Website also makes someone believe that 1.0.0 is already released, as there is no mention of the rc1 status.

To not confuse users, a stable image tag and the updated website/documentation should only be available after the release is out of the door.

System Info

N/A

Additional context

No response

Validations

  • Read the Contributing Guidelines.
  • Read the docs.
  • Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
  • Checked that the bug isn't fixed in the next version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]
  • Check that this is a concrete bug. For Q&A join our Discord Chat Server or the Matrix room.
@schewara schewara added the bug Something isn't working label Jul 27, 2023
@6543
Copy link
Member

6543 commented Jul 27, 2023

about v1.0 I created a pull to clarify it -> #2043

as for making v0.15 marked as unsupported. that was done at #2034 as the rc1 did not had any bugs/regressions that people did complained about since rc release. And we don't want new users to look at the docs and still use v0.15 - the code has matured in so many ways since then.

the real v1.0.0 will come soon as we fix the last incoming complains e.g. #2038

6543 added a commit that referenced this issue Jul 27, 2023
#2040 did point out, it needs to be better clarified
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants