Given that, would it be possible to have ELPA build from a separate branch?
That's how I organize some of my other packages, with a "stable" branch and
a master branch. If ELPA pulled from a "stable" branch, I could push a fix
to that while the next major version is still in development.
We can also do that, yes, using the `:release-branch`.
Okay, that sounds good to me. Please see the attached patch to
elpa-packages, which sets the release-branch to "stable".
Done, thanks.
Will this patch cause the package to be rebuilt for v0.4, or do I need to
make a v0.4.1 release to trigger that?
There's already a 0.4 package, and by design, packages never(!) get
rebuilt, so you'll need to change `Version:`, yes.
[ And currently, changes on the release branch are only pulled as
a side-effect of pulling changes from the devel branch, so if you only
commit to the release branch, the package may wait for a while until
it's actually released. :-( ]