Building emacs

So, I've been using emacs28 for some time now, which I build like this: ``` git clone git://git.sv.gnu.org/emacs.git && cd emacs git checkout emacs-28 && git pull ./autogen.sh ./configure --with-native-compilation --with-json \ --with-mailutils --with-imagemagick \ --with-x-toolkit=lucid \ CFLAGS="-O3 -mtune=native -march=native -fomit-frame-pointer" prefix=/usr/local make -j16 sudo make install ``` Now that emacs-28 is out, has anybody been using master (emacs-29)? If so, is it stable enough for prime use or should I wait a little longer?

I’ve been using emacs-29 on macOS since the bumped the version in the `master` branch, with new builds a few times a week. And so far no issues with my config. Overall issues with nightly builds are very rare, and when it does happen, it’s mostly due to rename or removed function or variable that some package I’m using depends on meaning the package will be updated soon, and in the meantime I can patch something hacky and temporary into my config.

I use versions of Emacs that I rebuild from the git master branch very frequently (and I mean it: I will generally pull and rebuild daily), because at one point in the past I was wanting to become a regular Emacs contributor. It is very rare that I run into any issues. I've had some instances in the past where being on the bleeding edge has in fact cut me a little bit from a package compatibility perspective, but I've enough Emacs Lisp under my belt to at least mitigate the worst of it, and honestly it hasn't even happened that often. Generally whatever problems I run into manifest as Emacs just plain 'not building' and I'll just use the last revision that did build (I install it to `~/local` mainly for such insulation purposes), but this is rare... like maybe every couple months rare. Running into issues that are not compatibility in nature like crashes is basically unheard of; I'm sure it's happened a handful of times, but probably only countable on one hand and I've been doing this for \~6-7 years now. Emacs from Git is almost always as stable as the regular releases. As long as you're willing to occasionally paper around some compatibility issues and be ready for the build to occasionally not work, I don't see the harm.