Kalle Olavi Niemitalo <[EMAIL PROTECTED]> writes: > 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.
I created an elinks-0.12 branch on 2007-04-22, and changed the version number of master to 0.13.GIT. I hoped that someone else would then add some of Witek's new features to 0.13.GIT while I'd fix 0.12-M1 bugs in 0.12.GIT. Unfortunately, there has been little activity in 0.13.GIT, apart from occasional merges from 0.12.GIT. Now, only bug 620 remains for 0.12-M1. And Witek has already fixed it in his branch, so it seems we could release 0.12pre1 next week. That version we could then also submit to the Translation Project, which likes stable URLs for packages: http://translationproject.org/html/maintainers.html After 0.12pre1, we'd fix the 0.12-M2 bugs, release 0.12rc1, etc. as quoted above. Now though, instead of opening 0.13.GIT, we'd merge the changes to the existing 0.13.GIT. Fonseca, do you accept this plan?
pgp60dpEs01Fp.pgp
Description: PGP signature
_______________________________________________ elinks-dev mailing list [email protected] http://linuxfromscratch.org/mailman/listinfo/elinks-dev
