Difference between revisions of "Krita/KritaLimeRoadmap"

Jump to: navigation, search
Line 1: Line 1:
== New Krita Lime repository ==
+
== New Krita Lime repository policy ==
  
 
New repository is located on:
 
New repository is located on:
Line 8: Line 8:
 
; "Somewhat stable builds" : developer starts rebuilding of a new testing package only when he is sure the new build is stable enough for people to use in their usual workflow. Therefore there are no automatic daily builds.
 
; "Somewhat stable builds" : developer starts rebuilding of a new testing package only when he is sure the new build is stable enough for people to use in their usual workflow. Therefore there are no automatic daily builds.
  
The repository contains:
+
=== The repository contains ===
  
 
# ktita-2.9 — latest official release of Krita. Corresponds to the latest 'tag' set by release manager.
 
# ktita-2.9 — latest official release of Krita. Corresponds to the latest 'tag' set by release manager.
Line 22: Line 22:
 
The repository was created using a private account, so it is updated manually by Dmitry Kazakov by means of recipes that fetch code directly from the new repository.
 
The repository was created using a private account, so it is updated manually by Dmitry Kazakov by means of recipes that fetch code directly from the new repository.
  
== Repository code layout ==
+
== Repository layout ==
  
 
=== Auto-tracking branches ===
 
=== Auto-tracking branches ===
  
* '''lp:~dimula73/calligra/calligra-2.9''' — auto-tracking branch of calligra/2.9 git branch
+
lp:~dimula73/calligra/calligra-2.9 — auto-tracking branch of calligra/2.9 git branch
* '''lp:~neon/calligra/master''' — auto-tracking branch of master git branch
+
lp:~neon/calligra/master — auto-tracking branch of master git branch
  
 
=== ''debian'' branches ===
 
=== ''debian'' branches ===
Line 56: Line 56:
 
  https://code.launchpad.net/~dimula73/+recipe/krita-2.9-daily-ocio
 
  https://code.launchpad.net/~dimula73/+recipe/krita-2.9-daily-ocio
 
  https://code.launchpad.net/~dimula73/+recipe/krita-testing-l10n-all-daily
 
  https://code.launchpad.net/~dimula73/+recipe/krita-testing-l10n-all-daily
 +
 +
== Repository transition roadmap ==
 +
 +
=== Initial fork (Dmitry or any volunteer) ===
 +
# move all 6 code repositories into the team
 +
# create 6 recipes that build packages from these branches and put into the repository owned by the team
 +
 +
=== Remove dependency on project-neon and install into /usr/ instead of /opt/project-neon/ ===
 +
# just fix it in ''debian'' repositories (volunteer?)
 +
 +
=== Automatic builds of l10n packages ===
 +
# write a manual how it is done right now (Dmitry)
 +
# automate (volunteer?)
 +
 +
=== Auto-sync older repo ===
 +
# Copy 6 recipes from the new repo that use exactly the same shared branches

Revision as of 15:27, 23 April 2015

New Krita Lime repository policy

New repository is located on:

https://launchpad.net/~kritalime/<repository name>

This repository is declared as official Krita Lime repository and published in all Krita media sources. It contains two kinds of packages: official releases and "somewhat stable" builds of current developers branch.

"Somewhat stable builds" 
developer starts rebuilding of a new testing package only when he is sure the new build is stable enough for people to use in their usual workflow. Therefore there are no automatic daily builds.

The repository contains

  1. ktita-2.9 — latest official release of Krita. Corresponds to the latest 'tag' set by release manager.
  2. krita-2.9-l10n — localization packages for krita-2.9
  3. krita-testing — latest "somewhat usable" package of the current development branch. Kicked off manually by developers when they think "master is stable enough". No automatic daily builds.
  4. krita-testing-l10n — localization packages for krita-testing

Old Krita Lime repository

Old repository is located on: https://launchpad.net/~dimula73/+archive/ubuntu/krita

The repository was created using a private account, so it is updated manually by Dmitry Kazakov by means of recipes that fetch code directly from the new repository.

Repository layout

Auto-tracking branches

lp:~dimula73/calligra/calligra-2.9 — auto-tracking branch of calligra/2.9 git branch
lp:~neon/calligra/master — auto-tracking branch of master git branch

debian branches

These branches are nested on the top the main source directory to add debian folder which describes the packaging data

for krita-2.9

lp:~dimula73/+junk/krita-2.9-ubuntu — Precise only
lp:~dimula73/+junk/krita-2.9-ubuntu-ocio
lp:~dimula73/+junk/krita-2.9-l10n-all

for krita-testing

lp:~dimula73/+junk/calligra-ubuntu — Precise only
lp:~dimula73/+junk/calligra-ubuntu-ocio
lp:~dimula73/+junk/krita-testing-l10n-all

Recipes

for krita-2.9

https://code.launchpad.net/~dimula73/+recipe/stable-krita-2.9 — Precise only
https://code.launchpad.net/~dimula73/+recipe/stable-krita-2.9-ocio
https://code.launchpad.net/~dimula73/+recipe/stable-krita-2.9-l10n-all

for krita-testing

https://code.launchpad.net/~dimula73/+recipe/krita-2.9-daily — Precise only
https://code.launchpad.net/~dimula73/+recipe/krita-2.9-daily-ocio
https://code.launchpad.net/~dimula73/+recipe/krita-testing-l10n-all-daily

Repository transition roadmap

Initial fork (Dmitry or any volunteer)

  1. move all 6 code repositories into the team
  2. create 6 recipes that build packages from these branches and put into the repository owned by the team

Remove dependency on project-neon and install into /usr/ instead of /opt/project-neon/

  1. just fix it in debian repositories (volunteer?)

Automatic builds of l10n packages

  1. write a manual how it is done right now (Dmitry)
  2. automate (volunteer?)

Auto-sync older repo

  1. Copy 6 recipes from the new repo that use exactly the same shared branches

Content is available under Creative Commons License SA 4.0 unless otherwise noted.