On Wed, Nov 10, 2010 at 02:55:19PM +0100, Reinhard Tartler wrote:
On Wed, Nov 10, 2010 at 14:06:10 (CET), Jonas Smedegaard wrote:
I propose the following:

  * As a minimum, the changelog is completely untouched until final
release, where the uploader auto-generates using "git-dch -R",   adjusts
by hand as needed, and commits the changes.

"completely untouched" is too strong, I think. Please put at least a
dummy changelog entry "start new upload" or something with the correct
version number, so that test builds end up with the correct version
number. This makes testing easier.

Test builds wind up with _wrong_ version number if using a version number of a not yet released package as-is.

If lowering the version number during test builds, then you can just as well do "git-dch --auto -S" and then "dch -l~0tartler".

  * Optionally intermediate updates to the changelog can be applied.
    Begin with "git-dch" and if that fails then instead use
    "git-dch --since <REF>" (replacing <REF> with reference to last
commit that touched debian/changelog), set distribution to
    UNRELEASED, and commit the changes.
  * Intermediate changelog updates are encouraged when release is
expected only later, and when more people work on same package.

In other words, I propose to replace the earlier commit style
(documented in the wiki?) of unconditionally adding UNRELEASED

[ "with the procedure above" is missing, I assume ]


- which does not work optimally together with git-dch IMO.

YMMV, but I think what you describe works well enough with git-dch.

You have good experience with git-dch auto-resolving after a manually added dummy UNRELEASED entry?

 - Jonas

 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

Attachment: signature.asc
Description: Digital signature

pkg-multimedia-maintainers mailing list

Reply via email to