Dear KDE people: The page https://projects.kde.org/projects/extragear/utils/krusader/repository/show?rev=plasma now works, although there it's written that the latest change (it was in the "plasma" branch) was made on this date: 2015-04-09 and that it was made by Davide Gianforte (the page https://projects.kde.org/projects/extragear/utils/krusader/activity says the same wrong outdated information (it wasn't Davide who made the latest change, and it wasn't on that date, maybe the problem has the same source). However, as anyone can see in http://quickgit.kde.org/index.php?p=krusader.git the latest activity (it was in the "plasma" branch) was made on this date: 2015-04-11 For more information, in that page, people can search for the text plasma click on the "shortlog" link that right next to it, and see that the latest activity was made by Raymond Wooninck. That date and author are the right ones, anyone can see the same doing something like this: git clone git://anongit.kde.org/krusader cd krusader git checkout plasma git log Thanks for all the good KDE work! Reproducible: Always
Note: Davide Gianforte wrote commits using the nickname "Gengis Dave".
This is because the process which updates projects.kde.org is too heavy in terms of server load and has been disabled. This is not viewed as a problem as we're in the process of replacing projects.kde.org.
> This is not viewed as a problem as we're in the process of replacing projects.kde.org. Showing false information one day, another day, another day, etc. is not viewed as a problem? How can be this bug set to "resolved" after being confirmed and waiting for the solution? Can people trust the web of KDE?
It is a problem, however the resources needed to keep the site up to date aren't worth the value it provides at this time. This is particularly the case when our newer system provides this.
More than a week has passed and those pages are still wrong and misleading KDE users. In similar cases, webmasters put e.g. some text to warn people instead of letting them being misled. I'm changing the status of this bug to "verified" because, as anyone can clearly see, this bug was confirmed, it was set to "resolved" while it was not, it is not, and people should trust KDE when KDE speaks, publishes information and so on. Thanks for KDE! Keep up the good work!