KPhotoAlbum: Difference between revisions

From KDE Community Wiki
(Import development topics from userbase)
 
No edit summary
Line 1: Line 1:
{{Construction}}
{{Construction}}


The user documentation for KPhotoAlbum is in the [https://userbase.kde.org/KPhotoAlbum userbase wiki].
The user documentation for [https://kphotoalbum.org KPhotoAlbum] is in the [https://userbase.kde.org/KPhotoAlbum userbase wiki]. There is also a [https://phabricator.kde.org/project/view/255/ project page] on phabricator.


== Active Git branches ==
== Active Git branches ==
Line 7: Line 7:
* ''master'' <br />Current development branch
* ''master'' <br />Current development branch
* ''5.x''<br />Branch tracked by [https://community.kde.org/Neon/Builder#The_Packaging Neon/stable].<br />When ''master'' is in stable condition, it should be synced to ''5.x'': {{Input|1=<nowiki>git checkout 5.x ; git merge master</nowiki>}}
* ''5.x''<br />Branch tracked by [https://community.kde.org/Neon/Builder#The_Packaging Neon/stable].<br />When ''master'' is in stable condition, it should be synced to ''5.x'': {{Input|1=<nowiki>git checkout 5.x ; git merge master</nowiki>}}
== Building KPhotoAlbum ==
* [[/build_instructions|Build instructions]]
== How to contribute ==
=== Patches ===
We accept patches vie email to our [https://mail.kdab.com//mailman/listinfo/kphotoalbum mailing list] and via [https://phabricator.kde.org/project/view/255/ phabricator]. To use the latter, we recommend using arcanist.


== How to do a release ==
== How to do a release ==

Revision as of 22:31, 7 February 2019

 
Under Construction
This is a new page, currently under construction!


The user documentation for KPhotoAlbum is in the userbase wiki. There is also a project page on phabricator.

Active Git branches

  • master
    Current development branch
  • 5.x
    Branch tracked by Neon/stable.
    When master is in stable condition, it should be synced to 5.x:
    git checkout 5.x ; git merge master

Building KPhotoAlbum

How to contribute

Patches

We accept patches vie email to our mailing list and via phabricator. To use the latter, we recommend using arcanist.

How to do a release

Preparing a release tarball

Building a snapshot tar ball is rather straight forward. Install the releaseme building tool and run a command to generate the source package.

git clone git://anongit.kde.org/releaseme
cd releaseme

To create the source package, run e. g.:

./tarme.rb --origin trunk --version 5.1 kphotoalbum

Steps for doing a release

KPA Release Steps

  • Update CMakeLists.txt with the new version number you are just about to tag
  • Update the ChangeLog to mark the new release and add the key improvements to the list of changes, if they are not already mentioned in the ChangeLog
  • Update doc/index.docbook to reflect the new release (if the documentation has been updated)
    <releaseinfo>4.5</releaseinfo>
  • Commit the last changes
    git commit -v -a
  • Tag the new release and push it out
    git tag -a -m "kpa 5.4 released" v5.4
    git push
    git push --tags
  • Create a tar ball of the released sources using the instructions on the following section (kphotoalbum.rb --version 5.4)
  • Upload the created tar ball to the incoming directory of upload.kde.org using an FTP client. The current instructions of notifying administrators of the upload are shown when logging in to the FTP server. You create a ticket and provide SHA sums and some other information of the upload.
  • Add a new version to Bugzilla (bugs.kde.org, you have to have administrator rights to do this): Edit Products → KPhotoAlbum → Add version
  • Publish the release information (KPA's web site, mailing lists, distributor's bugtracking system, social media etc.).** Don't forget to post on the kde-distro-packagers mailing list, and make sure to mention any changes in dependencies.**
  • Create a video of the cool new features and publish it on Youtube. A nice tool for doing so is recordmydesktop. If you uploaded such a video, don't forget to add it to the Videos page on the homepage (cf. the README_new_video.txt file).
  • Notify people building the binary packages for different distributions