Add a user-readable changelog #1005

New Issue

GiteaMirror · 2025-11-02T03:44:59-06:00

GiteaMirror commented

2025-11-02 03:44:59 -06:00

Originally created by @jonasfranz on GitHub (Aug 26, 2017).

The current changelog for 1.1-rc1 is very long. I think that it might be to much for "normal" users. Is it possible to add a summary at the beginning for the "key" features and bug fixes. Because "normal" users won't understand what currently changed.

Originally created by @jonasfranz on GitHub (Aug 26, 2017). The current changelog for 1.1-rc1 is very long. I think that it might be to much for "normal" users. Is it possible to add a summary at the beginning for the "key" features and bug fixes. Because "normal" users won't understand what currently changed.

GiteaMirror added the type/question label 2025-11-02 03:44:59 -06:00

GiteaMirror closed this issue

2025-11-02 03:45:00 -06:00

GiteaMirror commented

2025-11-02 03:45:00 -06:00

@lunny commented on GitHub (Aug 27, 2017):

Normally, we will post a blog to summarize the changelog.

@lunny commented on GitHub (Aug 27, 2017): Normally, we will post a blog to summarize the changelog.

GiteaMirror commented

2025-11-02 03:45:00 -06:00

@strk commented on GitHub (Aug 27, 2017):

I agree the CHANGELOG section should be more concise.
In particular I noticed many items referring to OpenID which
should instead appear only once (as OpenID support is new
in this release).

Jonas Franz: it'd be easier if you would send a PR, targetting
the 1.2 branch.

@strk commented on GitHub (Aug 27, 2017): I agree the CHANGELOG section should be more concise. In particular I noticed many items referring to OpenID which should instead appear only once (as OpenID support is new in this release). Jonas Franz: it'd be easier if you would send a PR, targetting the 1.2 branch.

GiteaMirror commented

2025-11-02 03:45:00 -06:00

@bkcsoft commented on GitHub (Aug 27, 2017):

Changelog should never be edited after it's been merged other that to remove old versions that are no longer tracked 🙁

@bkcsoft commented on GitHub (Aug 27, 2017): Changelog should never be edited after it's been merged other that to remove old versions that are no longer tracked 🙁

GiteaMirror commented

2025-11-02 03:45:01 -06:00

@bkcsoft commented on GitHub (Aug 27, 2017):

Also, listing the PRs that went in makes it easier to find what introduced a bug

@bkcsoft commented on GitHub (Aug 27, 2017): Also, listing the PRs that went in makes it easier to find what introduced a bug

GiteaMirror commented

2025-11-02 03:45:01 -06:00

@thehowl commented on GitHub (Jan 11, 2018):

I think that before the release we should probably go over everything and write a "Release Highlights" section, at least on the blog post. This way we can list the most significant changes; perhaps something like Godot's changelog. So that users don't just sigh and say "ugh, gitea wants me to update again", but rather "oh look, Gitea got an update!"

@thehowl commented on GitHub (Jan 11, 2018): I think that before the release we should probably go over everything and write a "Release Highlights" section, at least on the blog post. This way we can list the most significant changes; perhaps something like [Godot's changelog](https://godotengine.org/article/godot-reaches-2-1-stable). So that users don't just sigh and say "ugh, gitea wants me to update again", but rather "oh look, Gitea got an update!"

GiteaMirror commented

2025-11-02 03:45:01 -06:00

@lafriks commented on GitHub (Jan 11, 2018):

@thehowl it would be nice but we need someone who volunteers to write such blog posts as ours are quite boring as you know ;)

@lafriks commented on GitHub (Jan 11, 2018): @thehowl it would be nice but we need someone who volunteers to write such blog posts as ours are quite boring as you know ;)

GiteaMirror commented

2025-11-02 03:45:01 -06:00

@thehowl commented on GitHub (Jan 11, 2018):

Well then, I'll just have to get typing as the 25th approaches :)

@thehowl commented on GitHub (Jan 11, 2018): Well then, I'll just have to get typing as the 25th approaches :)

GiteaMirror referenced this issue

2025-11-02 11:52:45 -06:00

[PR #1005] [MERGED] Fix some links. #15706

Sign in to join this conversation.