In the developer documentation: add more files that have to be changed when a new Krusader version is released
Closed, ResolvedPublic

Description

In the developer documentation of https://phabricator.kde.org/w/krusader/release-howto/ we could add more files that have to be changed when a new Krusader version is released. For example, the text:

Set new version (and release name) in CMakeLists.txt and README

could be substituted by

Set new version (and release name) in those files:
    - CMakeLists.txt
    - README
    - NEWS
    - Changelog
    - doc/index.docbook
    - doc/features.docbook
    - doc/release-overview.docbook
    - (in some cases) doc-extras/ChangeLog
and several web pages:
    - https://krusader.org/get-krusader/release-archive/index.html
    - https://krusader.org/get-krusader/index.html
    - https://krusader.org
asensi created this task.May 8 2018, 6:14 PM
nmel claimed this task.May 9 2018, 7:04 AM
nmel added a subscriber: nmel.

I'll update this doc after the v2.7 release among some other things I found or will find.

asensi updated the task description. (Show Details)Jul 11 2018, 3:49 PM

Nikita, if you haven't got the time for this change, I can do the changes myself.

nmel added a comment.Jul 15 2018, 6:06 AM

Hi Toni,

I'm busy with some other projects, so don't have much time for Krusader these days. I started the work but then I realized I'll better fill in the details when I prepare the v2.7.1 release (in August?).

Feel free to add whatever you like, it just dev docs, we can reshape it later. Usual style for working with wiki docs — everyone can change but should focus on improving the pages (updating obsolete info, writing details, adding new sections, reshaping for readability, etc.) — let's follow this practice.

asensi closed this task as Resolved.Jul 15 2018, 7:15 PM

Thanks, Nikita, it's done :-) .

I prefer reviewing changes before applying them, but I understand that we often lack time :-)

nmel added a comment.Jul 17 2018, 5:15 AM

Thanks!

I prefer reviewing changes before applying them, but I understand that we often lack time :-)

For wiki changes, AFAIK, there is no tool for review and the content is not critical. We need to review repository changes though.