[Pkg-tigervnc-devel] Changelog practices

[Ola Lundqvist]

Hi again

One more thing that I think is a good practice. It is that whenever we
upload a new build we tag that version so we can easily find it.

I have used unstable/<versionnumberhere> when I have tagged so far.

I just uploaded and tagged like this:

git tag unstable/1.7.0+dfsg-1
git push origin --tags

If you do not push the tags with that special command they are not shared.

But I guess you know this practice already as I see quite a few tags. :-)

Best regards

// Ola

On 2 January 2017 at 23:11, Ola Lundqvist <opal at debian.org> wrote:
> Hi
>
> This is what I could find. It was not much I must admit.
>
> Regarding policy, see here:
> https://www.debian.org/doc/debian-policy/ch-source.html (chapter 4.4).
> Specifically see the footnote:
> https://www.debian.org/doc/debian-policy/footnotes.html#f15
>
> The footnote is the only one actually telling that history should not
> be rewritten.
>
> And some in the maintainers guide:
> https://www.debian.org/doc/manuals/maint-guide/dreq.en.html#changelog
> and
> https://www.debian.org/doc/manuals/maint-guide/update.en.html
>
> I can not find any source for my statement regarding (2) that you
> should not step revision many times. There are no such rules but I
> think it is a good practice anyway.
>
> The most important thing here is that we do not delete history. :-)
>
> // Ola
>
> On 2 January 2017 at 22:54, Joachim Falk <joachim.falk at gmx.de> wrote:
>> Hi all,
>>
>> Am 02.01.2017 um 22:27 schrieb Ola Lundqvist:
>>> Hi all Tigervnc package maintainers
>>>
>>> I'd like to ask for a little more stringent handling of the
>>> debian/changelog file.
>>> To my knowledge rewriting the changelog history (for more than
>>> spelling correction or similar) is a big no-no.
>> is there a policy documentation for how to handle debian changelog?
>>
>>> This did not matter much before the package reached Debian unstable
>>> but now that it has done so I have to ask you for the following:
>>> 1) Do not change changelog entries that have already been uploaded.
>>>   I guess it was you Liang Guo that did this when uploading the
>>> 1.7.0-dfsg version.
>>>  Please do not change such entries. Instead upload a new version.
>>> 2) Do not step revisions that have not been uploaded. In that case
>>> please just keep the version currently in use.
>>> 3) Keep the UNRELEASED target until you actually plan to do the
>>> upload. This is not very important but helps to make sure we can do 1
>>> and 2 above.
>>>
>>> With this said, I think you do a great job.
>>>
>>> I'm now changing to how it should look like.
>>>
>>> Best regards
>>>
>>> // Ola
>>
>> Regards,
>> Joachim Falk
>>
>>
>>
>> _______________________________________________
>> Pkg-tigervnc-devel mailing list
>> Pkg-tigervnc-devel at lists.alioth.debian.org
>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-tigervnc-devel
>
>
>
> --
>  --------------------- Ola Lundqvist ---------------------------
> /  opal at debian.org                     Folkebogatan 26          \
> |  ola at inguza.com                      654 68 KARLSTAD          |
> |  http://inguza.com/                  +46 (0)70-332 1551       |
> \  gpg/f.p.: 7090 A92B 18FE 7994 0C36  4FE4 18A1 B1CF 0FE5 3DD9 /
>  ---------------------------------------------------------------



-- 
 --------------------- Ola Lundqvist ---------------------------
/  opal at debian.org                     Folkebogatan 26          \
|  ola at inguza.com                      654 68 KARLSTAD          |
|  http://inguza.com/                  +46 (0)70-332 1551       |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36  4FE4 18A1 B1CF 0FE5 3DD9 /
 ---------------------------------------------------------------