K3b: Difference between revisions

From KDE Community Wiki
No edit summary
No edit summary
 
(13 intermediate revisions by 2 users not shown)
Line 1: Line 1:
'''[[/Getting Started |Getting Started]]'''
== Roadmap ==
== Roadmap ==
=== K3b 2.0 ===
=== K3b 2.0 ===
Line 7: Line 9:
* <strike>Porting audio player in CD audio project to QtMultimedia</strike>
* <strike>Porting audio player in CD audio project to QtMultimedia</strike>
* <strike>Porting DCOP interfaces to D-BUS</strike>
* <strike>Porting DCOP interfaces to D-BUS</strike>
* Support of KDE Plasma’s global progress bar and removal of K3b’s own progress OSD
* <strike>Support of KDE Plasma’s global progress bar and removal of K3b’s own progress OSD</strike>
* Support for writing Flash Drive images
* Support for writing Flash Drive images
* Spanning data projects over more than one disk
* Spanning data projects over more than one disk
Line 14: Line 16:
==Release Procedure==
==Release Procedure==
<ol>
<ol>
<li>Get <tt>[http://websvn.kde.org/trunk/KDE/kdesdk/scripts/createtarball createtarball]</tt> script"
<pre>svn checkout svn://anonsvn.kde.org/home/kde/trunk/extragear/multimedia/k3b .</pre></li>


<li>Edit <tt>config.ini</tt> file and update information in <tt>[k3b]</tt> section.</li>
<li>Get <tt>[https://projects.kde.org/projects/playground/sdk/releaseme releaseme]</tt> script:
<pre>git clone git://anongit.kde.org/releaseme
cd releaseme</pre></li>
 
<li>Edit <tt>k3brc</tt> file and update '''version''' entry.</li>


<li>Run:
<li>Run:
<pre>./create_tarball.rb -a k3b</pre></li>
<pre>./k3b.rb</pre>
The script fetches sources from git repository, translations from SVN and makes a source package. On success the script creates a source tarball, e.g. <tt>k3b-2.0.0.tar.bz2</tt>.</li>
 
<li> Make sure the version in <tt>CMakeLists.txt</tt>, <tt>README</tt>, <tt>INSTALL</tt> is valid.</li>
 
<li>Test the tarball. Uncompress and build it. In ideal case the compilation should be performed on vanilla environment (without any trace of K3b, minimal requirements with default environment variables etc.). After compilation check if the application runs.</li>
 
<li>Upload the tarball to the server ([http://sourceforge.net/projects/k3b Sourceforge]).</li>
 
<li>[https://bugs.kde.org/editversions.cgi?product=k3b Add new version] to the bug tracker.</li>
 
<li>Write release announcement and publish it on [http://k3b.org k3b.org]. Update download page.</li>
 
<li>Send an announcement email to:
* k3b@kde.org
 
<li>Update K3b status on software sites. Following sites needs an update:
* [http://sourceforge.net/projects/k3b Sourceforge]
* [http://freshmeat.net/projects/k3b Freshmeat]
* [http://kde-apps.org/content/show.php/K3b?content=9875 KDE-Apps.org]
</li>
 
</ol>
</ol>



Latest revision as of 17:58, 18 March 2016

Getting Started

Roadmap

K3b 2.0

K3b is about to be released: Announcement draft

K3b 2.1

  • Getting rid of KDE3Support classes
  • Porting audio player in CD audio project to QtMultimedia
  • Porting DCOP interfaces to D-BUS
  • Support of KDE Plasma’s global progress bar and removal of K3b’s own progress OSD
  • Support for writing Flash Drive images
  • Spanning data projects over more than one disk
  • DVD subtitle grabbing

Release Procedure

  1. Get releaseme script:
    git clone git://anongit.kde.org/releaseme
    cd releaseme
  2. Edit k3brc file and update version entry.
  3. Run:
    ./k3b.rb
    The script fetches sources from git repository, translations from SVN and makes a source package. On success the script creates a source tarball, e.g. k3b-2.0.0.tar.bz2.
  4. Make sure the version in CMakeLists.txt, README, INSTALL is valid.
  5. Test the tarball. Uncompress and build it. In ideal case the compilation should be performed on vanilla environment (without any trace of K3b, minimal requirements with default environment variables etc.). After compilation check if the application runs.
  6. Upload the tarball to the server (Sourceforge).
  7. Add new version to the bug tracker.
  8. Write release announcement and publish it on k3b.org. Update download page.
  9. Send an announcement email to:
  10. Update K3b status on software sites. Following sites needs an update:

Bug Tracker

K3b uses KDE Bugzilla to track bugs. Here you can find all bugs related to K3b.

Contact

If you have prepared a patch or just want to contact K3b developers please write to [email protected] mailing list. You can also catch them on #k3b on Freenode.

See Also