Re: how to manage d/changelog for updated but not yet sponsored package
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, that version is safe to resue as far as I'm concerned), but
> fold it into one entry when uploading to Debian proper.
>
> ${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.
VCS repo is very helpful in this case. It eliminates the need to increment
the version of the package. And change log will show real history of package
versions in Debian archive.
Best regards,
Boris
Reply to: