Umbrello Project • Project • Index

Umbrello Developer Resources

Table of content

  1. Bugs and feature requests
  2. Changelog
  3. How to contribute
  4. Umbrello continuous build status
  5. 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 it1. 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:

  1. Create a new bug.kde.org account if not available
  2. Implement the feature and create a merge request for https://invent.kde.org/kde/umbrello. See Gitlab project forking workflow for hints how to do.
  3. The related commit message should have the 'FIXED-IN:' and 'BUG:' keyword 1 e.g.
    FIXED-IN: 2.29.3 (KDE Release 19.08.3)
    BUG:12345
  4. 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:

  1. Create a new bug.kde.org account if not available
  2. Assign the related bug to yourself to indicate that you are working on this bug.
  3. Fix the bug and create a merge request for https://invent.kde.org/kde/umbrello. See Gitlab project forking workflow for hints how to do.
  4. The related commit message should have the 'FIXED-IN:' and 'BUG:' keyword1 e.g.
    FIXED-IN: 2.29.3 (KDE Release 19.08.3)
    BUG:12345
  5. After review has been approved, the reviewer will merge in the patch(es) to the related branch.

Umbrello continuous build status

KDE continuous build (Linux, FreeBSD, Windows MSVC)

Windows (cross compiled)

References

1.This is technical performed by the FIXED-IN git keyword.

Global navigation links