diff --git a/developers.php b/developers.php index 4d6c6c0..c19fdeb 100644 --- a/developers.php +++ b/developers.php @@ -1,132 +1,132 @@ $text\n

"; } function li_link($url, $text, $post="") { echo "
  • $text$post\n
  • "; } function li_jenkins_link($text, $job) { $url = "https://build.kde.org/job/$job"; $icon_url = "https://build.kde.org/job/$job/badge/icon?style=plastic"; echo "
  •  $text
  • "; } echo getContentList(__FILE__); ?>

    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.1 -In case you want to see, which bugs has been fixed in which version you may take a look at the +

    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

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

    How to contribute

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

    1. Create a new bug.kde.org account if not available
    2. Assign the related bug to yourself. This will change the state of the related bug to in Progress at the KDE Features Plan
    3. Implement the feature and submit it to KDE code review. KDE related documentation about how to use phabricator could be found at Infrastructure/Phabricator.
    4. -The related commit message should have the 'FIXED-IN:' and 'BUG:' keyword e.g. +The related commit message should have the 'FIXED-IN:' and 'BUG:' keyword 1 e.g.
      FIXED-IN: 2.25.3 (KDE Applications 18.04.3)
       BUG:12345
      -See a related KDE community page for more details.
    5. After review has been approved, the reviewer will apply the patch to the related branch or will give you instruction how to do.

    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 submit the patch to KDE code review. KDE related documentation about how to use phabricator could be found at Infrastructure/Phabricator.
    4. -The related commit message should have the 'FIXED-IN:' and 'BUG:' keyword e.g. +The related commit message should have the 'FIXED-IN:' and 'BUG:' keyword1 e.g.
      FIXED-IN: 2.25.3 (KDE Applications 18.04.3)
       BUG:12345
      -See a related KDE community page for more details.
    5. After review has been approved, the reviewer will apply the patch to the related branch or will give you instruction how to do.

    Umbrello continuous build status

    The KDE infrastructure provides a continuous build service, which performs a rebuild for every commit on configured projects. For Umbrello such rebuilds has been configured for the following branches:

    Linux OpenSUSE

    Windows MSVC

    +

    References

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