Re: how to manage d/changelog for updated but not yet sponsored package

2012-02-13 Thread Jakub Wilk
* Ben Finney ben+deb...@benfinney.id.au, 2012-02-13, 13:40: I want to keep trace of it in the d/changelog by keeping my first version entry and adding a second entry. Can I do that ? Will it confuse some Debian robots ? It's fine. I consider uploading the package to ‘mentors.debian.net’ a

Re: how to manage d/changelog for updated but not yet sponsored package

2012-02-13 Thread Charles Plessy
Le Mon, Feb 13, 2012 at 11:53:45AM +0100, Jakub Wilk a écrit : * Ben Finney ben+deb...@benfinney.id.au, 2012-02-13, 13:40: I want to keep trace of it in the d/changelog by keeping my first version entry and adding a second entry. Can I do that ? Will it confuse some Debian robots ? It's

Re: how to manage d/changelog for updated but not yet sponsored package

2012-02-13 Thread Gergely Nagy
Jakub Wilk jw...@debian.org writes: * Ben Finney ben+deb...@benfinney.id.au, 2012-02-13, 13:40: I want to keep trace of it in the d/changelog by keeping my first version entry and adding a second entry. Can I do that ? Will it confuse some Debian robots ? It's fine. I consider uploading the

Re: how to manage d/changelog for updated but not yet sponsored package

2012-02-13 Thread Boris Pek
Hi, Personally, I like the middleground best (though, I haven't been practicsing this yet, but this is how things would work in my ideal world): upload to mentors.d.n with incremental versions (when it makes sense; if the reviewer/potential sponsor spots a bug in a version not announced,

Re: how to manage d/changelog for updated but not yet sponsored package

2012-02-13 Thread Stephen M. Webb
On 02/13/2012 07:14 AM, Gergely Nagy wrote: ${VERSION}-${N}~mentors${X} for mentors, ${VERSION}-${N} for Debian proper. A little more work on both sides, but we get the best of both worlds with as little of the worst as possible. +1 -- Stephen M. Webb stephen.w...@bregmasoft.ca -- To

Re: how to manage d/changelog for updated but not yet sponsored package

2012-02-13 Thread Gergely Nagy
Boris Pek tehnic...@yandex.ru writes: Hi, Personally, I like the middleground best (though, I haven't been practicsing this yet, but this is how things would work in my ideal world): upload to mentors.d.n with incremental versions (when it makes sense; if the reviewer/potential sponsor

Re: how to manage d/changelog for updated but not yet sponsored package

2012-02-13 Thread Nicolas Dandrimont
Le 13/02/2012 à 13:14, Gergely Nagy alger...@balabit.hu écrivit : ${VERSION}-${N}~mentors${X} for mentors, ${VERSION}-${N} for Debian proper. A little more work on both sides, but we get the best of both worlds with as little of the worst as possible. Hi, This scheme is something I was

Re: how to manage d/changelog for updated but not yet sponsored package

2012-02-13 Thread Boris Pek
Depends on the situation. If it's a quick update, and I can followup within moments, then indeed, there is no reason to increment the version (see my when it makes sense comment above). But if hours, or even days can pass between iterations, then I much prefer a new version on mentors. That

Re: how to manage d/changelog for updated but not yet sponsored package

2012-02-13 Thread Gergely Nagy
Boris Pek tehnic...@yandex.ru writes: Depends on the situation. If it's a quick update, and I can followup within moments, then indeed, there is no reason to increment the version (see my when it makes sense comment above). But if hours, or even days can pass between iterations, then I much

Re: how to manage d/changelog for updated but not yet sponsored package

2012-02-13 Thread Gergely Nagy
Nicolas Dandrimont nicolas.dandrim...@crans.org writes: Le 13/02/2012 à 13:14, Gergely Nagy alger...@balabit.hu écrivit : ${VERSION}-${N}~mentors${X} for mentors, ${VERSION}-${N} for Debian proper. A little more work on both sides, but we get the best of both worlds with as little of the

Re: how to manage d/changelog for updated but not yet sponsored package

2012-02-13 Thread Jakub Wilk
* Charles Plessy ple...@debian.org, 2012-02-13, 20:07: I consider uploading the package to ‘mentors.debian.net’ a release of the package, since at that point interested people (e.g. reviewers) can rely on it, and the version should refer uniquely to what I uploaded at that time. Be aware,

how to manage d/changelog for updated but not yet sponsored package

2012-02-12 Thread Jerome BENOIT
Hello List: I am on the edge to put on m.d.n an updated version of one of my not yet sponsored packages: since between the two versions the upstream maintainer kindly integrated some patches that I submitted to him as Debian patches, I want to keep trace of it in the d/changelog by keeping my

Re: how to manage d/changelog for updated but not yet sponsored package

2012-02-12 Thread Ben Finney
Jerome BENOIT g62993...@rezozer.net writes: I want to keep trace of it in the d/changelog by keeping my first version entry and adding a second entry. Can I do that ? Will it confuse some Debian robots ? It's fine. I consider uploading the package to ‘mentors.debian.net’ a release of the