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

2.9.x: missing git tags #2446

Closed
kloczek opened this issue Feb 9, 2024 · 8 comments
Closed

2.9.x: missing git tags #2446

kloczek opened this issue Feb 9, 2024 · 8 comments
Labels
status: duplicate This issue or pull request already exists.

Comments

@kloczek
Copy link

kloczek commented Feb 9, 2024

Detailed Description of the Problem

Looks like in git repo are missimg git tags from 2.9.1 to 2.9.4.

Expected Behavior

Release version tags should be present in git repo.

Steps to Reproduce the Behavior

N/A

Do you have any idea what may have caused this?

No response

Do you have an idea how to solve the issue?

No response

What is your configuration?

N/A

Output of haproxy -vv

N/A

Last Outputs and Backtraces

No response

Additional Information

No response

@kloczek kloczek added status: needs-triage This issue needs to be triaged. type: bug This issue describes a bug. labels Feb 9, 2024
@chipitsine
Copy link
Member

looks duplicate of

#2303
#1318

@kloczek
Copy link
Author

kloczek commented Feb 9, 2024

Without those tags is not possible to track new releases using gt repo content.

BTW it would be nice if you would start create gh releases to make that easier.
On create github release entry is created email notification to those whom have set in your repo the web UI Watch->Releases.
gh release can contain additional comments (li changelog) or additional assets like release tar balls (by default it contains only assets from git tag) however all those part are not obligatory.
In simplest variant gh release can be empty because subiekt of the sent email contains git tag name.

I'm asking because my automation process uses those email notifications by trying to make preliminary automated upgrades of building packages, which allows saving some time on maintaining packaging procedures.
Probably other people may be interested to be instantly informed about release new version as well.

Documentation and examples of generate gh releases:
https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository
https://cli.github.com/manual/gh_release_upload/
jbms/sphinx-immaterial#282
https://github.com/marketplace/actions/github-release
https://pgjones.dev/blog/trusted-plublishing-2023/
jbms/sphinx-immaterial#281 (comment)
tox target to publish on pypi and make gh release https://github.com/jaraco/skeleton/blob/928e9a86d61d3a660948bcba7689f90216cc8243/tox.ini#L42-L58

@chipitsine
Copy link
Member

comment from

#1318 (comment)

describes current release scheme used

@capflam
Copy link
Member

capflam commented Feb 9, 2024

It is the 4th issue you open on the same subject (this one, #2303, #1318 and #2239). Same question, same response. We are only using GH as an issue tracker. The DEV repo is mirrored to ease issue tracking in commit messages.

@capflam capflam closed this as not planned Won't fix, can't repro, duplicate, stale Feb 9, 2024
@lukastribus lukastribus added status: invalid This issue is not within HAProxy itself. and removed type: bug This issue describes a bug. status: needs-triage This issue needs to be triaged. labels Feb 9, 2024
@git001
Copy link
Contributor

git001 commented Feb 9, 2024

The funny part is that the same user @kloczek have also raised the other issues before. 🤦‍♂️

@kloczek
Copy link
Author

kloczek commented Feb 10, 2024

The funny part is that the same user @kloczek have also raised the other issues before. 🤦‍♂️

Hmm .. but what is so funny in not tagging repo after release new version? 🤔
As I wrote before without those tags is not possible to detect that new version has been released.

@git001
Copy link
Contributor

git001 commented Feb 10, 2024

That people does not accept how a open source project handles GH. As in the last issues mentioned GH is only used for Issues. The answer here show a valid option to recognize new versions. Why isn't that an option for you to get informed about new versions?

@TimWolla TimWolla added status: duplicate This issue or pull request already exists. and removed status: invalid This issue is not within HAProxy itself. labels Feb 10, 2024
@lukastribus
Copy link
Member

We have discussed this over and over again, git stable trees are openely accessible with git tags marking bugfixes release, so there is nothing else to do here. I'm locking this issue now.

@haproxy haproxy locked as resolved and limited conversation to collaborators Feb 10, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: duplicate This issue or pull request already exists.
Projects
None yet
Development

No branches or pull requests

6 participants