[pacman-dev] release roadmap?
vmiklos at frugalware.org
Wed Feb 1 15:55:06 EST 2006
On Sun, Oct 30, 2005 at 06:46:14PM +0100, Aurelien Foret <aurelien at archlinux.org> wrote:
> The ORE tags from the file lib/libalpm/sync.c are placeholders for
> missing chunks of code.
> The commentaries associated with the tags were copied/pasted from
> commentaries in the pacman.c file from pacman 2.9.7 to remind me to
> implement the missing sections.
> Implementing code for these parts may not be obvious and may need to be
> This is the most important task to achieve before pacman 3.0 can be
imho this is now done
> On the library side, I really would like to have error messages and log
> callbacks be reviewed. pm_errno usage is missing in some parts of the
> code. manpages are needed too.
cmiiw, but these are solved, too
> Upon release, the library must be usable (documented, and errors
> returned to the frontend must be really clean).
> On pacman side, outputs should be checked too. The ORE tag in
> src/pacman/log.c must be fixed.
a patch to fix that ore tag is just sent
> Last, but not least, more tests are needed, especially for backward
> compatibility between pacman 2.9.x and the library.
this is something you can decide, i mean what tests fail
so it would be nice if we could make a new todo about what must be done
before the first 3.x release
udv / greetings,
Developer of Frugalware Linux, to make things frugal - http://frugalware.org
More information about the pacman-dev