The bugs blocking the ELinks 0.12.0 release are listed here: http://bugzilla.elinks.cz/buglist.cgi?target_milestone=0.12-M1&target_milestone=0.12-M2&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED
I think we should release 0.12pre1 when all the bugs targeted for 0.12-M1 have been fixed. Then people would update translations and test ELinks on various operating systems while we fix the 0.12-M2 bugs. Next, we'd release 0.12rc1, wait for reports, document the operating systems on which it was tested, release 0.12.0 with minimal changes, and open 0.13.GIT. That is, if the maintainer agrees. Lately, I've been busy reviewing the already reported bugs and testing which ELinks versions they affect and whether they have been fully fixed, in order to get accurate release notes for 0.12.0, and find out which fixes should be backported to 0.10.6.GIT or 0.11.2.GIT.
pgpKBKVwMiOgZ.pgp
Description: PGP signature
_______________________________________________ elinks-dev mailing list elinks-dev@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-dev
