Send inn-workers mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/inn-workers
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 inn-workers digest..."
Today's Topics:
1. Re: Please generate the ChangeLog file also for snapshots
(Julien ?LIE)
2. Re: INN Git tag format changed (Julien ?LIE)
3. Re: INN Git tag format changed (Russ Allbery)
4. Re: INN Git tag format changed (Julien ?LIE)
5. Re: INN Git tag format changed (Bo Lindbergh)
----------------------------------------------------------------------
Message: 1
Date: Fri, 17 Sep 2021 23:56:59 +0200
From: Julien ?LIE <[email protected]>
To: [email protected]
Subject: Re: Please generate the ChangeLog file also for snapshots
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
Hi Russ,
>> Following a discussion from last year, it is now the right time to
>> handle that request while updating snapshot generation.
>
> My feeling on this is that the Debian package shouldn't include the raw
> changelog. It's potentially huge and it feels like a waste of space. We
> maintain a fairly complete NEWS file that should already mention anything
> that people using INN need to know about what changed, and that's the
> useful file to install in the Debian package.
In debian/rules (in the Debian package), there previously was only
"dh_installchangelogs ChangeLog". The change last year seems fine as
NEWS is present in all cases.
override_dh_installchangelogs:
if [ -e ChangeLog ]; then \
dh_installchangelogs ChangeLog ; \
else \
dh_installchangelogs ; \
fi
As we plan to no longer ship ChangeLog, and NEWS is enough, there will
no longer be any need to override dh_installchangelogs for future INN
packages.
> I'd like to drop ChangeLog generation from releases as well. I know there
> were some objections here the last time I said that, but they seemed
> strange to me (IIRC, someone said they only read ChangeLog files because
> they don't trust NEWS files to be meaningful and, well, okay, but I don't
> think that's a good reason for us to do extra work to ship a ChangeLog
> file given that our NEWS file is meaningful).
Incidentally, it is now very easy with GitHub to browse that ChangeLog
and even look at code changes at the same time.
Tag comparison gives that:
https://github.com/InterNetNews/inn/compare/2.6.3...2.6.4
(Trac also permitted that, but not as user-friendly...)
--
Julien ?LIE
??You know what I did before I married? Anything I wanted to.??
------------------------------
Message: 2
Date: Sat, 18 Sep 2021 00:05:15 +0200
From: Julien ?LIE <[email protected]>
To: "[email protected]" <[email protected]>
Subject: Re: INN Git tag format changed
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
Hi all,
First of all, thanks Russ for the new tag format, which seems appropriate.
> I've pushed new bare version tags and deleted the release/* tags.
> (Figured best do that early on before anyone starts depending much on the
> new repository and format.)
Seems like the two tags now exist in my local repository.
% git show 2.6.4
commit 2f516bb12842591d3dbbc949bf97d349805fcdac (tag: release/2.6.4,
tag: 2.6.4)
I bet I need to reclone it.
Incidentally, I've tried to play with release notes associated to tags
in GitHub. Here is a suggestion of writing for 2.6.3 and 2.6.4:
https://github.com/InterNetNews/inn/releases
I thought the date of the release, a link to the GitHub diff, and 2
sections (Bug Fixes, New Features) would be good. For major releases,
an additional section for Breaking Changes, if any, would be added.
Any comments or things you would prefer? (before I go on with older
releases)
--
Julien ?LIE
??There's a way of transferring funds that is even faster than
electronic banking. It's called marriage.?? (Sam Kinison)
------------------------------
Message: 3
Date: Fri, 17 Sep 2021 15:30:47 -0700
From: Russ Allbery <[email protected]>
To: [email protected]
Subject: Re: INN Git tag format changed
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Julien ?LIE <[email protected]> writes:
> Seems like the two tags now exist in my local repository.
> % git show 2.6.4
> commit 2f516bb12842591d3dbbc949bf97d349805fcdac (tag: release/2.6.4, tag:
> 2.6.4)
> I bet I need to reclone it.
Yes, or manually delete the old tags. Git doesn't have a mechanism to
push tag deletion down to checkouts.
> Incidentally, I've tried to play with release notes associated to tags in
> GitHub. Here is a suggestion of writing for 2.6.3 and 2.6.4:
> https://github.com/InterNetNews/inn/releases
> I thought the date of the release, a link to the GitHub diff, and 2
> sections (Bug Fixes, New Features) would be good. For major releases,
> an additional section for Breaking Changes, if any, would be added.
> Any comments or things you would prefer? (before I go on with older
> releases)
This looks great! Thank you for doing that!
--
Russ Allbery ([email protected]) <https://www.eyrie.org/~eagle/>
Please send questions to the list rather than mailing me directly.
<https://www.eyrie.org/~eagle/faqs/questions.html> explains why.
------------------------------
Message: 4
Date: Sat, 18 Sep 2021 09:20:05 +0200
From: Julien ?LIE <[email protected]>
To: [email protected]
Subject: Re: INN Git tag format changed
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
Hi Russ,
>> Seems like the two tags now exist in my local repository.
>>
>> % git show 2.6.4
>> commit 2f516bb12842591d3dbbc949bf97d349805fcdac (tag: release/2.6.4, tag:
>> 2.6.4)
>>
>> I bet I need to reclone it.
>
> Yes, or manually delete the old tags. Git doesn't have a mechanism to
> push tag deletion down to checkouts.
Oh, indeed "git tag -d release/..." worked fine. I thought git would
have then wanted to push something to the remote repository. I thought
wrong and should read more the Manual :-) Issue solved, thanks!
As for tags for INN 1.x we only have 1.5.1 (like in SVN).
We discussed it in 2015. The initial CVS repository was made with 1.5.1
and then an import of 1.8-current so we do not have source history for
intermediate versions like 1.5.1sec2, 1.6b3 and 1.7.x:
https://lists.isc.org/pipermail/inn-workers/2015-May/018474.html
So we can't do more for tagging 1.x releases.
Well let's keep it as-is, and available old tarballs in ftp.isc.org if
that's fine for everyone.
>> Incidentally, I've tried to play with release notes associated to tags in
>> GitHub. Here is a suggestion of writing for 2.6.3 and 2.6.4:
>> https://github.com/InterNetNews/inn/releases
>>
>> I thought the date of the release, a link to the GitHub diff, and 2
>> sections (Bug Fixes, New Features) would be good. For major releases,
>> an additional section for Breaking Changes, if any, would be added.
>
>> Any comments or things you would prefer? (before I go on with older
>> releases)
>
> This looks great! Thank you for doing that!
OK, thanks for your feedback.
I'll add the previous releases little by little :)
--
Julien ?LIE
??Les id?es fausses ne sont pas toujours mauvaises.?? (Marcel Aym?)
------------------------------
Message: 5
Date: Sat, 18 Sep 2021 10:22:01 +0200
From: Bo Lindbergh <[email protected]>
To: [email protected]
Subject: Re: INN Git tag format changed
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Quoth Russ Allbery <[email protected]>:
> Git doesn't have a mechanism to push tag deletion down to checkouts.
git fetch --prune-tags
/Bo Lindbergh
------------------------------
Subject: Digest Footer
_______________________________________________
inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers
------------------------------
End of inn-workers Digest, Vol 133, Issue 9
*******************************************
