Am Wed, 22 Sep 2021 19:53:15 +0200 schrieb ess-help-requ...@r-project.org: > Message: 2 > Date: Wed, 22 Sep 2021 07:26:59 -0500 > From: Dirk Eddelbuettel <e...@debian.org> > To: "Sparapani, Rodney" <rspar...@mcw.edu> > Cc: "ess-help@r-project.org" <ess-help@r-project.org> > Subject: Re: [ESS] Advice on setting up ESS to edit and knit Rmarkdown > files > Message-ID: <24907.8467.529784.900...@rob.eddelbuettel.com> > Content-Type: text/plain; charset="us-ascii" > > > On 20 September 2021 at 13:59, Sparapani, Rodney via ESS-help wrote: > | Generally, this stuff should just work out-of-the-box. > > Understood. > > | And we are not a company like RStudio so this FOSS setup works for > us as | developers and hopefully it still serves the users well. > > But legal structure has nothing to with 'calling a release'. Which is > done by authors (who should know the code better than users) saying > "yep what we have at HEAD right now is good" and then cut a tarball. > That is a _marker_. Which some less-informed people like me can take > (and then ship downstream to Debian, and with that Ubuntu etc). > > Without a marker, no shipment. Less ideal to me and others.
This! As Dirk says: No release, no packages in distros. I would happily update ess in openSUSE, but as a user it is very hard (impossible?) to find out what the status of ess is. As was commented in another message even the internal release numbers are not consistent. Looking forward to a 21.11 release :-) And thx for all your work! Detlef > > So pretty-please if someone would: could a release one of these > moons. It does not have to be frequent or regularly schedule or > anything. But maybe more often than once every few years? Maybe > when you sync with upstream Emacs (assuming you do now)? > > Dirk > ______________________________________________ ESS-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/ess-help
