[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1036832: marked as done (should have update date near the title)

Your message dated Sun, 16 Feb 2025 06:54:24 +0100
with message-id <91e01bb5-f205-48b3-b1b5-c9c152dc09e1@debian.org>
and subject line Re: Bug#1036832: should have update date near the title
has caused the Debian Bug report #1036832,
regarding should have update date near the title
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1036832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036832
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release-notes
Severity: minor

Hi,

while talking to Paul, we have found out that it might be a good idea to
teach our users that the release notes DO get updated after the release,
something that even I didn't know after 20 years of Debian.

Having the date of last update (of the English translation) prominently
visible, preferable on the first screen of release notes being
displayed, would be a good idea to share this information that way.

Greetings
Marc

--- End Message ---
--- Begin Message --- 
Hi,

On 16-02-2025 01:09, Holger Wansing wrote:

The shown date should say, when the last change in *English* has happened;
changes to translations would not have to be taken into account here.



Agree.


I have prepared a merge request for this:
https://salsa.debian.org/ddp-team/release-notes/-/merge_requests/217



Merged.
Thanks. This was somewhere on my TODO list where I never got around to actually do. 

Paul

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: