I mean I don't care that much, I can create a repo in the org and move it there (and open up maintainers list), but it seems to me one could just as well pick it up from HEAD of v2 or master. Just trying to understand.
(There's a lot more that could be done on emacs support for beancount. Especially around thing-at-point functionality) On Wed, Oct 7, 2020, 06:47 Martin Blais <[email protected]> wrote: > Does a MELPA (or other) release have to be tied to a beancount tag? > > On Wed, Oct 7, 2020, 06:38 Stefano Zacchiroli <[email protected]> wrote: > >> On Wed, Oct 07, 2020 at 06:20:04AM -0400, Martin Blais wrote: >> > Given its small size, a whole dedicated repo is a bit much, don't you >> think? >> > Always happy to take patches. >> >> The main point is release independence. I'd love to be able to receive >> beancount.el releases (e.g., via MELPA or similar repos) without having >> to wait for a Beancount release. In fact, as a user, I don't see why >> the release processes of the two should be tightly coupled at all. >> >> git repositories are cheap. >> >> Cheers >> -- >> Stefano Zacchiroli . [email protected] . 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 [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/beancount/20201007103846.ln2sbaekba4nsnck%40upsilon.cc >> . >> > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/CAK21%2BhON%3DvRm8%3D1TB%3D3Z91R_8%2Bcfp0xZxdQQSj3YzYXrUuCjng%40mail.gmail.com.
