off-topic: i wonder whether it'd be a simple change for the list notification mails here to also include a deeplink to the web version of the list messages in their context (similar to the Pd list mails)? or am I just too blind to find them?
cheers, Ben On Tue, Mar 17, 2026, 11:09 IOhannes m zmoelnig via GEM-dev < [email protected]> wrote: > On 3/17/26 10:37, Ben Wesch wrote: > > On Tue, Mar 17, 2026 at 7:44 AM cyrille henry via GEM-dev > > <[email protected]> wrote: > >> > >> "PS: and yes, sorry for the delays. i'm better with monitoring github > issues these days :-)" > >> So I just use github since. > > > > thanks for chiming in, cyrille! i wasn't aware of this - will stick to > > github as well from now on. > > > it's slightly more complicated than that. > > i'm still fine with using the mailinglist. > it's just that my mailserver sorts all my mailinglist mails into > dedicated folders (e.g. "development/GEM" or somesuch), and given the > low activity of this mailinglist i don't open this folder as much as i > used to - and so I might miss things. > > > > >> the last release is 0.94-snapshot from 2026 02 25. I.E 3 weeks ago. > > > > i know - and also, the snapshot is the only version people get by > > default from deken. so it's not really a big issue. but i think that > > "snapshot" doesn't reflect the amount of work that went into Gem since > > 2019. :) > > > i totally agree. > > the big question is: do you - as the users - consider the current state > of Gem stable enough for a release? > > what's your stance about RC-bugs? > (a feeble list of which can be seen on [1]) > > fmgadsr > IOhannes > > [1] > < > https://github.com/umlaeute/Gem/issues?q=is%3Aissue%20state%3Aopen%20label%3Arelease-critical > > > > -- > please do not CC me for list-emails > > _______________________________________________ > GEM-dev mailing list -- [email protected] > To unsubscribe send an email to [email protected] >
_______________________________________________ GEM-dev mailing list -- [email protected] To unsubscribe send an email to [email protected]
