Re: GNUnet 0.21.0 released

Hi,

On 07.03.24 14:09, [email protected] wrote:
> Hello,
> 
> 
> first of all,
> GNUnet 0.21.0 - finally brought to this part of the multiverse, that's a
> biggy. Lots of important work went into it for reaching this point - among
> others integration of TNG, right?
> Virtual applause to all devs contributing to this!
> 
> This important news item -
> https://www.gnunet.org/en/news/2024-03-0.21.0.html - hasn't appeared on
> the info-gnu mailing list, yet:
> https://lists.gnu.org/archive/html/info-gnu/2024-03/threads.html
> 
> A look into the info-gnu mailing list archive reveals that news of previous
> GNUnet version publications did appear on this mailing list - for example
> GNUnet 0.12.0, on Fri, 20 Dec 2019 10:28:59 +0900:
> https://lists.gnu.org/archive/cgi-bin/namazu.cgi?query=GNUnet&submit=Search%21&idxname=info-gnu&max=20&result=normal&sort=date%3Alate
> 
> But planet gnu got it: https://planet.gnu.org/

It is easier to do the news entry first, and that is automatically 
distributed to planet.gnu.org (RSS).
I never got around to writing that script that parses the .j2 file into 
a plain text that can be sent via email.

> 
> This is a major major release, so please make sure that said news item to
> it also gets on the info-gnu mailing list.
> 
> And in the long run—suggestion for improvement:
> This kind of instance has a history, all together sketching an outlook for
> process improvement by automation, whenever a major release is on the
> table.
> Can't there be any kind of script created, pushing the according news item
> to planet gnu and the info-gnu mailing list all together just by the push
> of 1 button?
> So that not only Martin(?) or tesserakt(?) are eased from this specific
> task, but also all important spots are covered with this kind of news item
> securely at the same, immediate time?
> 
> Last time that got addressed, Martin replied
> 
> "Still, writing both the email AND the news post is tedious, so it would
> be nice to only write it once, from a template, and then generate both. Or
> generate one out of the other, without having to actually send HTML email.
> 
> 
> That being said, I would actually prefer to only send the link to the news
> entry, even for major releases. That is the simplest solution.
> 
> 
> BR" -
> https://lists.gnu.org/archive/html/gnunet-developers/2023-09/msg00004.html
> 
> What's status regarding that?
> 


It is true that just sending the link is easier. But for a major release 
we should just send the whole message in order to better distribute it 
to people that would otherwise not follow the link occasionally (i.e. 
for major releases).

> 
> Reasoning:
> This release is a quite important milestone among all releases, and
> therefore deserves to get spotlight according to that.
> 

Yes, but we already do that: Minor releases only go to our mailing lists 
with a link to the news, major releases get a full email.
The email will always be delayed a bit, as I use the news entry as template.

BR

> 
> Best regards,
> Bastian Schmidt
> 
>