Arash Esbati <ar...@gnu.org> writes: >>>> • Archive current master as auctex-13, and keep main as default branch. >>>> This means that every commit generates a new release on ELPA-devel. >>>> • Archive current master as auctex-13, and introduce a new intermediate >>>> default branch, say develop or some such. And then merge into main on >>>> a regular basis. >>> >>> My only comment is that I think it'd still be valuable to keep having >>> stable releases (published through ELPA) every now and then, just as >>> it is now, and not go full "every commit is a release" mode. >> >> That's already the case. Every pushed commit on the main branch [1] >> results in a new release in the GNU-devel ELPA repository for the >> adventurous users and every change in the Version header results in a >> release in the stable GNU ELPA repository. >> >> Of course, if major changes are to be made, one can still split a new >> feature branch off main where changes have no effect on what's published >> until they are done and merged back to main. > > So you say we should go for the first option?
Yes. That's the whole point of the GNU-devel repository: to allow adventurous users to try out the bleeding edge versions which hopefully report bugs as soon as possible. >> (I just saw that we changed the "[Unreleased]" heading to "[14.0.6] - >> 2024-06-30" after publishing 14.0.6. A chance to improve next >> time. :-)) > > Yes, mea culpa. Hopefully things work out better next time. Haha, no problem. :-) Bye, Tassilo
