Request History
dheidler created request
Version 1.11.50
factory-auto added opensuse-review-team as a reviewer
Please review sources
factory-auto accepted review
Check script succeeded
staging-bot added openSUSE:Factory:Staging:adi:7 as a reviewer
Being evaluated by staging project "openSUSE:Factory:Staging:adi:7"
staging-bot accepted review
Picked "openSUSE:Factory:Staging:adi:7"
licensedigger accepted review
The legal review is accepted preliminary. The package may require actions later on.
dimstar declined review
Please be a bit more verbose in the changes entry ... (not just version number).
Please read https://en.opensuse.org/openSUSE:Howto_write_good_changes for more details about a good changelog entry.
dimstar declined request
Please be a bit more verbose in the changes entry ... (not just version number).
Please read https://en.opensuse.org/openSUSE:Howto_write_good_changes for more details about a good changelog entry.
anag+factory reopened request
Reopened via staging workflow.
anag+factory added factory-staging as a reviewer
Being evaluated by group "factory-staging"
anag+factory accepted review
Unstaged from project "openSUSE:Factory:Staging:adi:7"
anag+factory declined request
Declined via staging workflow.
dheidler reopened request
Upstream changelog is empty as well.
I guess the update is only to track the new element-web version (both always share the same version number).
anag+factory added openSUSE:Factory:Staging:adi:62 as a reviewer
Being evaluated by staging project "openSUSE:Factory:Staging:adi:62"
anag+factory accepted review
Picked "openSUSE:Factory:Staging:adi:62"
mstrigl accepted review
Accepted review for by_group opensuse-review-team request 1128211 from user anag+factory
anag+factory accepted review
Staging Project openSUSE:Factory:Staging:adi:62 got accepted.
anag+factory approved review
Staging Project openSUSE:Factory:Staging:adi:62 got accepted.
anag+factory accepted request
Staging Project openSUSE:Factory:Staging:adi:62 got accepted.
from https://en.opensuse.org/openSUSE:Creating_a_changes_file_(RPM)#Version_updates
1. First of all, find out what is new or has changed. Non-exhaustive list of potential sources for newsworthy items: Files inside the source tree with a name of, or similar to, NEWS, CHANGES, ChangeLog the homepage of the project a blog about the software / a blog by the author an announce post on a mailing list, community/news sites like freshcode.club or LWN your own experience with the new version. 2. If you cannot find anything in the aforementioned set of places, that is ok. Say so, and consider it done. (For example, “* No changelog was made available.”) It is not necessary to inspect commit logs or to analyze source code.2 seems to be very applicable here