On Sat, Jan 05, 2019 at 08:29:32PM +1100, Martin Blais wrote: > Beyond baking a release for Beancount, is there anything else that's needed > to be patched in?
Not really. For dogfooding reasons I've myself switched to use the packaged version rather than the mercurial checkout and I haven't noticed anything missing or too annoying, even in light of long term support. Baking a release would be nice. It's not strictly needed, but it'd indeed give users more confidence they're not building on top of a shaky VCS snapshot. Another nice to have would be documentation shipped with the package, to allow for offline reading, which is something generally expected for Debian packages. Right now I'm only shipping this README: https://bitbucket.org/blais/beancount/src/ccc6dff1b7b4c29c48d41f666c0850ce2ce66bb7/docs/README?at=default&fileviewer=file-view-default I understand it's probably too short time to properly bake the documentation using the Google Docs -> rst pipeline, but maybe you'd consider shipping a one-off rst export with the upcoming release? Again, nothing blocking, just a nice to have if it's doable with little effort. Cheers -- Stefano Zacchiroli . z...@upsilon.cc . upsilon.cc/zack . . o . . . o . o Computer Science Professor . CTO Software Heritage . . . . . o . . . o o Former Debian Project Leader & OSI Board Director . . . o o o . . . o . « the first rule of tautology club is the first rule of tautology club » -- You received this message because you are subscribed to the Google Groups "Beancount" group. To unsubscribe from this group and stop receiving emails from it, send an email to beancount+unsubscr...@googlegroups.com. To post to this group, send email to beancount@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/20190105102908.r56exzjagqiucruh%40upsilon.cc. For more options, visit https://groups.google.com/d/optout.
