Hi Darcy, We sure can discuss how to improve the release cycle.
But it is not possible to fix every single bug before releasing a new version. We can use fix part of them and fix more of them in a subsequent version. I agree that we should do more testing before releases as well. Denis systematically runs a series of tests before every new version, but we could extend the tests both in number and in quality. Best wishes, --Joris On Sat, Dec 07, 2019 at 05:58:04PM +0800, Darcy Shen via Texmacs-dev wrote: > For the Scala Project, developers will write a detailed release issue: > > > > https://github.com/scala/scala-dev/issues/649 > > > > I think it is a good practice to write an open issue(ticket???for the release > process. > > > > We just write done things we have to do before the release and after the > release. > > > > For example, before the release, we should check the usability of basic > functionalities of GNU TeXmacs??? > > 1. Copy and Paste (Unicode) > > 2. Search and Replace (Unicode) > > 3. Import of various image formats (png, jpg) > > 4. ...... > > > > After the release, we may write a detailed release note and advertise GNU > TeXmacs somewhere on the internet. > > > > And also, it would be nice to use release candidates, when release candidates > are released, only bug fixes are allowed. > _______________________________________________ > Texmacs-dev mailing list > Texmacs-dev@gnu.org > https://lists.gnu.org/mailman/listinfo/texmacs-dev _______________________________________________ Texmacs-dev mailing list Texmacs-dev@gnu.org https://lists.gnu.org/mailman/listinfo/texmacs-dev
