[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[libredwg] contributions v1.2 available

From: Thien-Thi Nguyen
Subject: [libredwg] contributions v1.2 available
Date: Sat, 20 Feb 2010 23:29:00 +0100

These are in <> (libredwg), as usual.
Below is sample output from the create-changelog script.
Feedback welcome!

Thoughts on next steps:
 v2 -- add "configure --enable-tracing"
 v3 -- get "make check" working
 v4 -- get "make installcheck" working ("make install" probably ok?)
 v5 -- get "make dist" working
       At this point, we can remove support for "pre-regenerated
       tarballs" and instead post "snapshot releases".  This is
       preferable because such releases are very similar to an
       "official" release (from pov of end-user config, build).
 v6 -- get "make distcheck" working
 v7 -- packaging for gnusense, etc.

In the meantime, while i'm concentrating on these support mechanisms,
perhaps pitanga and juca could answer some policy questions:

 - What are the version numbering schemes for LibreDWG?
   - repository tags
   - project version
   - shared-object library version

 - Should "configure --enable-tracing" be yes or no by default?

 - What is the criteria for declaring a stable API (for bindings)?

 - What is the documentation strategy (doxygen, hand-write, ...)?

$ cd ~/build/GNU/libredwg
$ build/create-changelog.el --since master
Generating master..
2010-02-20  Thien-Thi Nguyen  <address@hidden>

        [admin] Add script to create ChangeLog from "git log" output.
        * build/create-changelog.el: New file.
        * HACKING (change log maintenance): Update.

2010-02-19  Thien-Thi Nguyen  <address@hidden>

        [admin] Add a program to create/publish pre-regenerated tarballs.
        * build/snap.GNUmakefile: New file.
        * build/.placeholder: Delete file -- no longer necessary.
        * .gitignore: Update ignorance.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]