Commit 6a0481ec authored by Nikita Melnichenko's avatar Nikita Melnichenko

Transitioned Phabricator wiki to dev-docs dir and updated content

Resolved #2.
parents 53118141 6effaeb5
# Krusader Development Documentation
This reference will help you to get started with Krusader development.
## Krusader resources for users
* [Project homepage](
* [Release downloads](
* [User mailing-list]( — for user questions, tracked by maintainers, answered by users and maintainers
* [System & Utilities forum on]( — user questions rarely appear here, answered by forum community
* [Bugzilla]( — all bugs and wishes are tracked here
* [Krusader extensions]( — user-contributed styles and user actions
* [Krusader app page on](
## Krusader resources for developers
* [Developer mailing-list]( — for development discussion and questions
* [Repository](
* [Repository mirror on GitHub]( — pull requests are ignored here
* [Automatic builds](
* [Krazy: static code analysis](
* [Krusader coding style]( — same style as for Frameworks
* [Release Howto]( — step-by-step release guide
* [ website repository]( — the website is deployed via CI from this repo
### General KDE development resources
* [KDE developer mailing-list](
* [KDE general announcements mailing-list](
* [KDE applications release announcements mailing-list]([we announce]( Krusader releases here
* IRC-channel: — for quick questions regarding anything related to KDE development
* [Git hooks for KDE Bugzilla]( — use these keywords in your commits
* [Closing issues through commit messages]( — add "Resolved #xxx" in a commit message to close a GitLab issue automatically
### Krusader dependencies
* [KIO API]( — KIO is heavily used for file related operations (local and remote).
* [KIO repository](
* [KBookmarks repository]( — used for editing Krusader bookmarks
### Recommended IDE and developer tools
* [KDevelop IDE](
* [Qt Creator IDE](
* [Cuttlefish]( — a useful icon browser for KDE
### Recommended reading
* [Qt Howto pages](
* [Qt New Signal Slot Syntax](
* [Freedesktop icon names]( — official cross-DE icon names, please try to use these first and fallback to the icon names included in Breeze to be more independent from specific icon themes
## Contributing
### Quick guide
1. Get a [KDE identity account](
2. Fork the [Krusader repository](
3. Clone your fork to your dev box.
4. Make changes in your local repository in a branch.
5. Push your branch to the fork.
6. Create a merge request (aka pull request) to the main repo, mark it with "Needs Review" label.
7. Wait for devs to review and resolve all comments.
8. Once the label is changed to "Approved" and all threads are resolved, devs will merge your change to the main repo.
Find more details in [Forking workflow](
### Commit guidelines
Familiarize yourself with commit message style by reading several commit messages in the repository. Notice that for simple changes we use single commits and for multiple related changes we use branches and merge them into master with a descriptive merge commit message.
If your change fixes a bug reported on, use both the `FIXED:` keyword with the bug number in square brackets and bug title, and `BUG:` keyword that triggers the Git hook to close the bug. Refer to an example below.
Your change must be reviewed and approved before you can push it to master branch.
You must adhere to [Krusader coding style]( and use the best coding practices.
Your commit (or branch merge if your change is a series of commits) must contain the code review link. It's recommended to place it on the last line and separate it from summary with an empty line. For example:
One-line commit title
Description of the change. The change description
FIXED: [ 123456 ] Bug title in case you fixed a bug
BUG: 123456
Gitlab understands the discussion link and nicely [integrates it]( into the UI like this: utilities/krusader!7 ([see example commit](9198345c62ff6c2337fb37c9913bff933f57414b)).
Once you push the commit to the repository, it will be automatically discovered by the Gitlab and it will close the merge request.
If your changes are important enough to be included in the ChangeLog, please add a line to the commit message beginning with one of these keywords {`FIXED:`, `ADDED:`, `CHANGED:`, `REMOVED:`} and a description. For example:
CHANGED: When the big red button is pressed, foo is activated and not bar anymore
This line should not be the title of the commit message.
If your change spreads across multiple commits, use the keywords and discussion link in the merge commit message.
Keep in mind that the link and the keywords should go to either your single commit or branch merge commit, i.e. only appear once in history.
Check git history and ChangeLog for more examples of using the keywords.
If your change contains multiple commits, which you'd like to keep, and you are still on top of master, please use `--no-ff` to keep it as a branch merge:
git checkout master && git merge --no-ff feature/new-foobar-widget
and then amend the commit message accordingly. Substitute `master` with your base branch if needed.
### FAQ
> I want to fix a bug but there is no bug report for it yet. Do I need to file one?
No, not if you are certain that it really is a bug. Feel free to just submit a review.
> I am unsure about the right approach to solve an issue, what is the best place to discuss?
Ask us on the [developer mailing list](
> How do I start tracking Krusader bug reports?
1. Sign-in to [Bugzilla](
2. Go to Preferences → Email Preferences tab.
3. On the "User Watching" section add `` to your watch list.
# Krusader Release Howto
This is a step-by-step release guide intended to streamline release process.
Don't follow this blindly though. Think, test and improve the guide as the process changes!
Many of the steps refer to the previous development system — the Phabricator.
Please update the guide as you follow the steps for releasing the next version.
## Overall release process
* Write a letter to krusader-devel group to claim yourself as a release manager, ask if there are any outstanding issues, code reviews, unpublished work that devs want to include into the release. Wait for a week to gather replies. Examples: [v2.7.0](, [v2.7.1](
* Discuss the proposed changes, set a feature freeze for the release (no new features should be included to the release later except the agreed on at this stage or bug fixes). Agree on the approximate release date. Examples: [v2.7.0](, [v2.7.1](
* Wait for changes to be reviewed and pushed.
* Discuss and pick a release name in case of major or minor release. Bug fix releases carry the release name over.
* Create a release branch if needed (see the corresponding section below).
* Update or ask to update the documentation. Check if changes made from the previous release have been documented. Update features for major or minor release (example: [v2.7.0](
* Propose the release date (for example, 3 weeks from now), update the docs and AppStream files. Examples: [v2.7.2](
* Declare the string freeze and doc freeze stage for 2 weeks and notify translators. Examples: [v2.7.1](!topic/krusader-devel/Fe5bOeTbCCo).
* Update change logs and news in the meantime. Examples: [v2.7.0](, [v2.7.1](
* Prepare review: version update. Examples: [v2.7.1](
* Prepare review: website update. Examples: [v2.7.1](
* On the release date: prepare and release the package (see the corresponding section below).
* Wrap up: cleanup and check a few things (see the corresponding section below).
## Environment
These steps assume that you set the developer access up already.
### First time setup
mkdir -v krusader-release-env && cd krusader-release-env
git clone
git clone
### Refresh
cd krusader-release-env
cd krusader && git checkout stable && git pull ; cd ..
cd kde-dev-scripts && git pull ; cd ..
## Create a release branch
In case you're doing a minor or major release (i.e. 2.7 -> 2.8 or 2.8 -> 3.0), `stable` branch needs to be remapped.
For example, you are going to do 2.7 -> 2.8. Then
1. First create a branch at the same point as `stable` to mark a past release branch. Name it `2.7`.
2. Hard reset stable to `master`
3. Create a commit in `master` updating the app version to `2.9.0-dev` (`stable` should keep previous master version which is `2.8.0-dev`, so no commit is needed)
4. Push `master`, `2.7` and `stable` to central repo in this order.
Now you are ready for the release.
In case you're doing patch version update (i.e. 2.7.1 -> 2.7.2), no update to stable branch is needed.
## Code Review: Documentation and AppStream files
Update the following files with new release version, date, name (if applicable) and features (if applicable):
* `doc/index.docbook`
* `doc/features.docbook`
* `doc/release-overview.docbook`
* `krusader/org.kde.krusader.appdata.xml`
**This must be pushed before doc freeze email.**
## Code Review: ChangeLog and NEWS update
Update the following files accordingly:
* `Changelog`
* `NEWS`
* `doc-extras/ChangeLog`
Search in git log for changelog messages and add them to the `ChangeLog` file:
cd krusader
git log $LAST_VERSION.. | grep 'FIXED:\|ADDED:\|UPDATED:\|CHANGED:\|REMOVED:' | sort
Add changes from bugzilla bug reports and code reviews manually if necessary.
## Code Review: Version bump
Update the following files with new release version, date, name (if applicable):
* `CMakeLists.txt`
**Verify that the version is building without warnings for both Debug and Release targets.
Verify it's running correctly and you don't see any obvious problems.
Do this ahead of time to be able to fix problems early!**
## Code Review: Website update
Update the following pages:
* `index.html`
* `get-krusader/release-archive/index.html`
* `get-krusader/index.html`
* `release/{VERSION}/changelog.txt`
* `release/{VERSION}/release_notes.txt`
Copy release notes and changelog from NEWS and ChangeLog accordingly.
## On the release date
### Verify the branch
Starting from version 2.7.1 we release only from the `stable` branch.
cd krusader && git checkout stable && git pull
Verify that ChangeLog and NEWS update is pushed or push it.
### Commit and push version updates
Apply version bump commit and tag it:
VERSION=`cat CMakeLists.txt | grep 'set(VERSION' | awk -F '"' '{print $2; }'`
git tag -a v${VERSION} -m "Tagging krusader-${VERSION}"
Don't push it right away! First edit `CMakeLists.txt` to change version to development version
(for example, for v2.7.1 release put `2.7.2-dev` there). Commit. Check everything is good:
git log
Now push with tags:
git push --follow-tags
This way ensures there are no commits in between version bumps.
### Create tarball
Update `kde-dev-scripts/createtarball/config.ini` with
gitTag = vX.Y.Z
version = X.Y.Z
and do
cd ../kde-dev-scripts/createtarball/
./create_tarball_kf5.rb -n -a krusader
mv -vi krusader-$VERSION ../..
mv -vi krusader-$VERSION.tar.xz ../..
cd ../../
### Test the package
**Corrupted translated documentation can break compiling, it's mandatory to do this step!**
mkdir -v build-${VERSION} && cd build-${VERSION} && cmake -DCMAKE_INSTALL_PREFIX=../install-${VERSION} -DQT_PLUGIN_INSTALL_DIR=../install-${VERSION} ../krusader-${VERSION} && make -j 3 && make install ; cd ..
Go to `Help -> About Krusader` and verify the version.
### Upload the package to a KDE server
curl -T krusader-${VERSION}.tar.xz
### Create a Sysadmin Request
Create a new Sysadmin Request asking to publish the package.
sha256sum krusader-${VERSION}.tar.xz
Example task: [Krusader v2.7.1 release](
Task template:
Dear Sysadmin,
**Package pending for Krusader**
New release for the Krusader project. The package is uploaded to
Desired destination: stable/krusader/{VERSION}
Full link:{VERSION}/krusader-{VERSION}.tar.xz
SHA256: {SHA256}
**Please add this release to the list of Krusader versions on**
We ask them to add versions on Bugzilla since the *editcomponents* permission is needed.
This permission allows to change settings for ALL projects.
Therefore only sysadmins can do this and nobody of the Krusader devs.
### Update the package checksum in the website change
Earlier, when you create the CR for the website change, you didn't know the hash of the package since you haven't created a package yet. Now you know it, and it's a good time to update it while you wait for response from admins.
Example: [v2.7.1 checksum update](
### Wait for the package to propagate on KDE servers
Once admins upload the package, they will close the ticket. You need to wait until you see some mirrors become available and then you can distribute the package.
### Update the Krusader website
Simply push your changes to repository and they'll become available as soon as some recurrent job notices the change and publishes the update. May take from a few minutes to a few hours (sometimes recurrent job is down) - usually it's very quick. If your changes are not deployed in 2 hours, create a sysadmin ticket about it.
### Send a letter to mailing lists
Once the website is updated, send a letter to the following mailing lists:
Please get the permission to post ahead of time.
## Wrap up
### Push createtarball config
The changes you made in `kde-dev-scripts` needs to be pushed to the master branch.
Example commit for [v2.7.1](
### Check if bugzilla is updated accordingly
[Click here]( and check if new version is present in the list.
### Merge your new version tag to master
Since `stable` contains changes not present in `master` (ChangeLog and documentation changes at least), you need to deliver them to the `master` branch. Merge your vX.Y.Z tag into the branch and resolve conflicts in places where version specified. Keep Krusader version that is in `master` during the conflict resolution.
Example merge for [v2.7.1](
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment