Kokua:Development

This page contains links and information related to Kokua Viewer development. For Imprudence Viewer development, see Imprudence:Development.


 * Reporting a bug
 * Proposing a feature

Using autobuild to compile
Building with autobuild (short outline)

Kokua Developer Workflow DRAFT
A Working Environment

Adding a queue to a bitbucket mercurial repo

 * Start with a Bitbucket (Bb) repository. Either new or fork an existing one.
 * From the Overview tab, select patch queue and in most cases check omit series.
 * You may want to make this a Private repository as it will hold your work in progress.
 * Similar to forking, Bb will work to make your queue.

Cloning a queue to your local system

 * When Bb finishes the queue, work shifts to your local system.
 * the just completed queue.
 * This is a clone of you main repository and a structured empty MQ repository.
 * The main repository is in its named directory and is now your work repository.
 * The MQ repository exists in  and it has an   directory for MQ commits.
 * The directory  holds named patches and a couple housekeeping files.
 * Edits to  and   files may be needed to customize the workflow.
 * I think it may be a Bb bug, but after,   has a default location of the queue versus the main and is not where you should   and   from. In the test environment, I used a pristine local repository for the   location and the Bb main repository for  . The MQ repository   has a   of the Bb queue, so no edits are required for it.

Interacting with the local queue

 * . This places an empty named patch in
 * work on and edit your sources
 * To update  file that is in.
 * work on and edit your sources some more
 * To update  file that is in   again.
 * removes the working tree changes. Similar to . But, the working tree can be set back to its last patched state with hg qpush. Or, you can reorder things by named patches otherwise you work from top of the working tree stack and the MQ stack. Commands   and   are in reference to the working tree stack.
 * If your patch is valuable and may be of use again, you can commit it and push it to the queue on Bb.  it off the working tree stack,   it is now revision control   to view details and   puts in the Bb queue repository.

Pushing changes to the remote queue or remote repository on bitbucket

 * Now to close the loop. We  onto the working tree and tested and all is as we desire.   takes the patch and makes a main repository commit and removes it as as named patch from.
 * displays data about the new  and then   sends it along to the Bb main repository.
 * Now generate a pull request for upstream for my-really-cool-patch.

older

 * Getting Kokua Source Code
 * Compiling Kokua
 * Compiling Kokua for Linux
 * Compiling Kokua for Mac
 * Git Primer

Communication Channels
These are the most relevant communication channels for viewer development:


 * Issue Tracker
 * IRC
 * Mailing Lists
 * ImpDev Meetups

Technical Documentation

 * Getting a backtrace with GDB