Skip to content

Commit

Permalink
Turned TODO into mini-bugzilla, README.developers updates.
Browse files Browse the repository at this point in the history
git-svn-id: svn+ssh://jackaudio.org/trunk/jack@300 0c269be4-1314-0410-8aa9-9f06e86f4224
  • Loading branch information
kaiv committed Jan 28, 2003
1 parent 0031e61 commit 501f5f1
Show file tree
Hide file tree
Showing 2 changed files with 64 additions and 11 deletions.
40 changes: 38 additions & 2 deletions README.developers
Expand Up @@ -13,6 +13,34 @@ development. If you have questions, or would like to make
changes, raise the issue on jackit-devel (see
http://jackit.sourceforge.net/lists ).

---------------------------------------------------------------------
Contents
-----------------------------------------------------------------------

- What is this?
- Version numbers
- Important files for developers
- Sending patches
- CVS Access
- Decision Process

-----------------------------------------------------------------------
Important files for developers
-----------------------------------------------------------------------

AUTHORS
List of contributors. If you have contributed code, mail Paul
Davis to get your name added to the list, or if you have
CVS-access, help yourself. :)
README.developers
This file.
TODO
A one file mini-bugzilla for JACK developers. Contains a list
of open and closed items. You can update this directly or
contact Kai Vehmanen if you don't have CVS access.
libjack/ChangeLog
A list of _all_ changes to the public interface!

-----------------------------------------------------------------------
Version numbers
-----------------------------------------------------------------------
Expand All @@ -31,7 +59,7 @@ to CVS:
changes are made

2. Client API versioning

JACK clients are affected by two interfaces, the JACK Client API (libjack)
and the JACK Client Protocol API (interface between jackd and
libjack). The former one is versioned using libtool interface
Expand All @@ -44,12 +72,20 @@ to CVS:
age = current libjack is both source and binary compatible with
libjack interfaces current,current-1,...,current-age

Note! It was decided in January 2003 that current interface number
will remain as zero until the first stable JACK version
is released.

JACK Client Protocol is versioned... <TBD>.

Note! All changes that affect the libjack API must be documented
in jack/libjack/ChangeLog using the standard ChangeLog style
(see GNU developer docs).

---------------------------------------------------------------------
Important files
-----------------------------------------------------------------------

---------------------------------------------------------------------
Sending patches
-----------------------------------------------------------------------
Expand Down Expand Up @@ -77,7 +113,7 @@ common sense is recommended. ;)
CVS Access
-----------------------------------------------------------------------

<TBD>
Contact Paul Davis.

---------------------------------------------------------------------
Uses of external libraries and other packages
Expand Down
35 changes: 26 additions & 9 deletions TODO
@@ -1,14 +1,31 @@
TODO
=======================================================================
*** TODO - A one file mini-bugzilla for JACK developers ***
=======================================================================

- figure out how to have pools of buffers for ports by type
- proper handling of client return values in libjack
- passing args to drivers and clients?
- getting callbacks and args from dynamically loaded clients?
- how do dynamically loaded clients (un)register ports, activate, etc.
- pool based malloc for rt client-local mem allocation
Version: $Id$

TO THINK ABOUT:
-----------------------------------------------------------------------

TO BE DECIDED (owner)

- dropping the use of CAP_RESOURCE (nando)

TODO (owner)

- figure out how to have pools of buffers for ports by type (pbd)
- proper handling of client return values in libjack (kaiv)
- passing args to drivers and clients? (pbd)
- getting callbacks and args from dynamically loaded clients? (pbd)
- how do dynamically loaded clients (un)register ports, activate, etc. (pbd)
- pool based malloc for rt client-local mem allocation (pbd)

TO THINK ABOUT

- multiple port buffer shm segments (i.e. dynamically
increase the total number of ports in the system)
increase the total number of ports in the system)

CLOSED (date,who,comment)

- call time client before all others (28.01.2003, kaiv, another solution)

-----------------------------------------------------------------------

0 comments on commit 501f5f1

Please sign in to comment.