Umbrello Developer Resources

Table of content

Bugs and feature requests
Changelog
How to contribute
Binary Factory
Windows (cross compiled)
Links

Bugs and feature requests

You may take a look at the wishlist, the junior jobs and/or the open bugs:

Changelog

When bugs get fixed or features are implemented, the related release version is assigned to it¹. In case you want to see, which bugs has been fixed in which version you may take a look at

How to contribute

If you want to implement a feature already listed in the wish list please:

Create a new bug.kde.org account if not available
Implement the feature and create a merge request for https://invent.kde.org/sdk/umbrello. See Gitlab project forking workflow for hints how to do.
The related commit message should have the 'FIXED-IN:' and 'BUG:' keyword ¹ e.g.
```
FIXED-IN: 2.29.3 (KDE Release 19.08.3)
BUG:12345
```
After review has been approved, the reviewer will merge in the patch(es) to the related branch.

In case you are going to fix an annoying bug in umbrello listed in the above mentioned bug list please:

Create a new bug.kde.org account if not available
Assign the related bug to yourself to indicate that you are working on this bug.
Fix the bug and create a merge request for https://invent.kde.org/sdk/umbrello. See Gitlab project forking workflow for hints how to do.
The related commit message should have the 'FIXED-IN:' and 'BUG:' keyword¹ e.g.
```
FIXED-IN: 2.29.3 (KDE Release 19.08.3)
BUG:12345
```
After review has been approved, the reviewer will merge in the patch(es) to the related branch.
The normal procedure is to merge stable branches into the master branch, i.e. bugs should be fixed in the stable branch.

Binary Factory

Win64 nightly build (git master, approx 1 day delay)

Windows (cross compiled)

Umbrello snapshot packages from Open Build Service.

References

^1.This is technically achieved by the FIXED-IN keyword in the commit message.