Send kea-dev mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/kea-dev
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of kea-dev digest..."
Today's Topics:
1. Re: Tweaking Kea development process proposal (Tomek Mrugalski)
2. Re: Tweaking Kea development process proposal (Francis Dupont)
3. Re: Tweaking Kea development process proposal (Tomek Mrugalski)
----------------------------------------------------------------------
Message: 1
Date: Mon, 14 Oct 2019 14:37:24 +0200
From: Tomek Mrugalski <[email protected]>
To: Francis Dupont <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [kea-dev] Tweaking Kea development process proposal
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
On 13/10/2019 19:23, Francis Dupont wrote:
> How does this work with entries from before Gitlab? Should we split the
> ChangeLog intp two parts?
The old entries would remain as they are.
No, I don't want to split changelog into separate files, especially with
the monthly releases. Changelog is a documented history of the project.
It should be kept as a single file.
Markdown is really an annotated text file. You can still clearly read it
in the console. What would change is the slight format, like perhaps add
spaces, a dash or a star, but overall the change would look the same.
See Stork changelog proposal as an example:
https://gitlab.isc.org/isc-projects/stork/blob/17-changelog/ChangeLog.md
If you click on edit (or get the source code), the underlying file is
still a very readable plain text file.
Tomek
------------------------------
Message: 2
Date: Mon, 14 Oct 2019 14:53:46 +0000
From: Francis Dupont <[email protected]>
To: Tomek Mrugalski <[email protected]>
Cc: Francis Dupont <[email protected]>, "[email protected]"
<[email protected]>
Subject: Re: [kea-dev] Tweaking Kea development process proposal
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
Tomek Mrugalski writes:
> See Stork changelog proposal as an example:
>
> https://gitlab.isc.org/isc-projects/stork/blob/17-changelog/ChangeLog.md
>
> If you click on edit (or get the source code), the underlying file is
> still a very readable plain text file.
=> yes for this file it works well but unfortunately it is not the case
for the Kea ChangeLog: if the links are not messed the log numbers are.
This does not mean that it will never work but just remaning the file
is clearly too simple / not enough.
Regards
Francis Dupont <[email protected]>
------------------------------
Message: 3
Date: Mon, 14 Oct 2019 18:42:36 +0200
From: Tomek Mrugalski <[email protected]>
To: Francis Dupont <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [kea-dev] Tweaking Kea development process proposal
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
On 14/10/2019 16:53, Francis Dupont wrote:
> => yes for this file it works well but unfortunately it is not the case
> for the Kea ChangeLog: if the links are not messed the log numbers are.
> This does not mean that it will never work but just remaning the file
> is clearly too simple / not enough.
I know. Markdown is a bit dumb. It takes the first number and considers
it start of a list and then counts forward. This breaks down the numbering.
But I've solved this in stork by adding extra character in front of the
number. Simple and works. Also this is something that can be done with a
script.
There's another problem, though. Gitlab is slow to parse 400KB+ markdown
file. But this is something we can't do much about.
Tomek
------------------------------
Subject: Digest Footer
_______________________________________________
kea-dev mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-dev
------------------------------
End of kea-dev Digest, Vol 64, Issue 3
**************************************
