Hi all,
today i noticed how pip manages its change-logs in a pretty interesting way,
they manage the fragments to be composed before a release in the folder
"news" in files named like "$ticketnumber.$changetype"
before a release those files get take out and composed into the change-log.
The fabu
Hi Ronny,
I definitely like the idea! I agree our current CHANGELOG maintenance could
use some improvement. :)
We could introduce it for `3.1`, what do you think?
On Tue, Mar 21, 2017 at 5:54 AM Ronny Pfannschmidt <
[email protected]> wrote:
> Hi all,
>
> today i noticed how pip m
Hey Ronny,
Oh you are absolutely right.
Do you know what happens with the old CHANGELOG entries btw?
Cheers,
On Tue, Mar 21, 2017 at 12:29 PM Ronny Pfannschmidt <
[email protected]> wrote:
> Hi Bruno,
>
> due to its Nature its best suited for introducing right after 3.1
>
> after
Hi Bruno,
due to its Nature its best suited for introducing right after 3.1
after all the before bits are already in place
-- Ronny
On 21.03.2017 14:41, Bruno Oliveira wrote:
Hi Ronny,
I definitely like the idea! I agree our current CHANGELOG maintenance
could use some improvement. :)
We co
Hi Bruno
towncrier takes the new entries, renders them to a text and then inserts
them either at the start, or right after a special marker line
-- Ronny
On 21.03.2017 16:32, Bruno Oliveira wrote:
> Hey Ronny,
>
> Oh you are absolutely right.
>
> Do you know what happens with the old CHANGELOG
Sounds great then! :)
Cheers
On Tue, Mar 21, 2017 at 1:14 PM Ronny Pfannschmidt <
[email protected]> wrote:
> Hi Bruno
>
> towncrier takes the new entries, renders them to a text and then inserts
> them either at the start, or right after a special marker line
>
> -- Ronny
>
> On 2