>Depends on the value of "from time to time" and the branch you're >checking out.
I could checkout the emacs-team branch, and update emacs-next to the commit in my channel every sunday (if time permits). >We don't work with master, but the branch for emacs N+1, >where N is the currently stable emacs. >We also tend to prefer release >candidates, but would surely like a bump when major things are >happening. Oh, I see. I can't find the branch/tag for Emacs 31, so is it safe for me to assume that the packages were updated because of a "major thing"? >major things I'll take a look at the commit history, then send a patch when I find: * bug fixes * features (Emacs Lisp additions, not C code or documentation) Besides these, do you think it's a good idea to not update during deprecations? There is talk[1] of deprecating Semantic[2] for example. Should I hold on submitting patches after this is commited? [1] <https://lists.gnu.org/archive/html/emacs-devel/2025-03/msg00678.html> [2] <https://www.gnu.org/software/emacs/manual/html_node/emacs/Semantic.html> -- Gabriel Santos
