[00:48] <guiverc> in this issue has picked up "UWN Issue 927 January 11-17 2026."  not usual I think
[00:51] <Bashing-om> guiverc: not unual at all ;; also lost here: Ubuntu 25.04 (Plucky Puffin): "Release team (on mailing list, Utkarsh Gupta on Ubuntu Discourse)" A dangling thought ?
[00:52] <guiverc> plucky eol:  s/wherein 25.04/wherein Ubuntu 25.04/ I suggest
[00:52] <guiverc> there are two annoucements from the Ubuntu Release Team; Ural did the ML and Utkarsh posted the later one on Ubuntu Discourse.
[00:53] <guiverc> for most it's the same person who does both so only one name.. I could have ignored the Ubuntu Discouse being posted by a different person, but felt if readers clicked that link they may get confused given differnt poster/name
[00:55] <guiverc> Personally I'd like to move the Edubuntu & Studio EOL notices above the 9to5/Marius one; even if a lower level (same indent currently) - you agree?
[00:56] <guiverc> we list edubuntu 25.04 EOL twice anyway; one has to go
[00:58]  * guiverc goes :( when I see optimize-swap one; -2 is its ranking anyway and 3/5 towards closure.. but askubu is way down on usage recent months as more goes to UD thus the inclusion I guess...
[01:01] <guiverc> server gazette:  i suggest dropping comma in "who helped her, with this post."
[01:04] <guiverc> the adjusted last sentences has me a tad confused.. "Sally makes the conclusion for using AI as it is all in the setup. One pays for the ease of use on the back end."  okay to you?  or "Sally concludes that using AI is all in the setup, with payments often appearing in the back end.  (also I'd be tempted to put "mostly in the setup" (not all in the setup) too but I'd have to re-read the article to be sure
[01:12] <Bashing-om> editing :)
[01:14]  * guiverc paused reading actually.. 
[01:16] <guiverc> resolute rebuild:  "and warns us that most aren’t new features just package rebuilds." read okay; I'm pausing after 'new features, just package rebuilds" as if it needs comma  (or an 'and')  already an and in that sentence so don't want another.. okay or add comma?
[01:18] <guiverc> gnome 50...  "(X11 backend is dropped)"   we use back-end earlier & 'backend' there?? yuk; add hypen? or remove from other back-end... we could also just drop "(X11 backend is dropped)" too as I think its redundant...
[01:20] <guiverc> gnome 49.3:  of no importance, but should "GNOME 49.3 Desktop release" have a lower case "desktop"??
[01:25] <Bashing-om> a pause is good - adding the comma.
[01:33] <Bashing-om> Next!
[01:33] <guiverc> sorry phone call & paused reading..
[01:34] <Bashing-om> just marking where I am at editing... // be aware arthritus tearing me up again - serious headack so my focus is lacking.
[01:35] <guiverc> gnome 49.3  suggest dropping 'far' from "he release of GNOME 48.8 and its far more ‘limited’ changes"
[01:36] <guiverc> he is the.. i just copy/pasted & missed the 't'
[01:38] <guiverc> nvidia wayland.. maybe s/acknowledge improvements/acknowledging improvements
[01:39] <guiverc> but do drop "details" from "details are provided."  (just after ack improvements)
[01:40] <guiverc> my suggestion anyway ^  you modified what I originally had, but the word "details' sticks on as wrong to me as I read it now ...
[01:41] <guiverc> nvidia 590; maybe s/ build into the Ubuntu multiverse/ build for the Ubuntu multiverse/ ??  ie. s/into/for/??  or s/into/in/  .. reading awkward to me (today)
[01:43] <Bashing-om> "With a quote"  if we drop details then the sentence no longer makes sense.
[01:45] <guiverc> which one.. mentally have moved one & can't recall what I said.. 
[01:48] <Bashing-om> ^ Ubuntu 26.04 Aims To Deliver: details can not drop details less we rewrite the sentence.
[01:53] <guiverc> "A quote from (Daniel van Vugt), a Mutter merge request and subsequent comments (acknowledging improvements) are provided" maybe?
[01:55] <guiverc> do what you think is best  (in noble updates currently)
[02:00] <Bashing-om> 53 dupes found - so far.
[02:00] <guiverc> at end... I will amend https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Archive so it points to https://discourse.ubuntu.com/c/uwn/uwn-issues/419 (not current going to uwn-issues)
[02:00] <guiverc> you did well Bashing-om ; I found NO dups
[02:01] <Bashing-om> wonder of wonders - distraught anf distracted as I have been - come on pain pills !
[02:02] <Bashing-om> saving what we have for your 3rd look :P
[02:06] <guiverc> thanks... much happer with 25.04 listing
[02:08] <guiverc> looks good to me Bashing-om , thanks
[02:09] <Bashing-om> More thanks goes to you - usuns dew eet/ Pass it on next to Jane.
=== guiverc2 is now known as guiverc
[20:58] <Bashing-om> Opening 927; prepping to publish - will start the push soonest.
[21:38] <Bashing-om> M/L is away - moving 927 to archive.
[21:39] <Bashing-om> setting up 928.
[21:50] <Bashing-om> 928 off and running.
[22:02] <guiverc> `grep ^# discourse.post` looks fine (927; don't always mention running that)
[22:04] <Bashing-om> guiverc: Might be good to verify the M/L - Google AI intrusion - took me 3 tries to make AI leave me to my busseness :)
[22:06] <guiverc> issue 927 sent to ubuntu-news@lists.ubuntu.com in my inbox (gmail) sent 27 mins ago it says
[22:06] <Bashing-om> looks sane ?
[22:08] <guiverc> tweeted 927, (mewe) & telegram
[22:08] <guiverc> looks fine to me Bashing-om (email copy; very long lines what I notice most)
[22:10] <Bashing-om> Making up a Mastodon blog next. // email great ! note never follow/allow any prompting in the email client! What we have is what we want.
[22:11] <Bashing-om> though I do run the issue through the spell checker.
[22:26] <Bashing-om> Mastodon Blogdid-ed / now to clean up and set up my local.
[22:58] <guiverc> uwn 927 posted to fb
[23:06] <guiverc> my check of https://ubuntu.com/community/uwn/ubuntu-weekly-newsletter-issue-927 discovered the UWN-work-in-progress was still visible...  thus removed (finally)
[23:07]  * guiverc hadn't noticed that earlier..
[23:13] <Bashing-om> guiverc: I do try and check that in my processes "WIP" is also removed - it's that tree for all the forest :(
[23:16] <guiverc> I know & realize that... we're human & thus make mistakes... procedures are there to help us, but we'll stick miss stuff on occasion, thus the checks/rechecks etc..  it was caught (eventually!)
[23:18] <Bashing-om> :D