Jonas Fonseca <[EMAIL PROTECTED]> writes: > Sounds good if somebody else is interested in starting the release > process of 0.12 and master.
Okay, I will try to follow doc/release.txt in a local branch off elinks-0.12. > I don't know if it would make sense to start migrating to use > Google Code for hosting the downloads. Personally, I am not willing to accept the confidentiality and export control clauses in the Terms of Service of Google Code. I would much rather pay for hosting elsewhere. > 0.12 and master seem to have already diverged quite a bit: > > 180 files changed, 4400 insertions(+), 2229 deletions(-) > > just for src/. Any thoughts about this? In my opinion, this has always > (at least once the number of committers grew) been ELinks' problem. The > gab between stable/unstable are very big, which makes making new > releases and upgrading very painful. I don't think 0.13.GIT has many regressions compared to 0.12.GIT. After 0.12.0 has been released, we may be able to get 0.13.0 out in a few months. Why do you think upgrading is painful? AFAIK, the only configuration incompatibility between 0.12.GIT and 0.13.GIT is the removed protocol.fsp.sort option, and that we could mitigate by disabling the warnings about unrecognized options. Are there some new library dependencies that are not listed in NEWS?
pgp0BJVodq82D.pgp
Description: PGP signature
_______________________________________________ elinks-dev mailing list [email protected] http://linuxfromscratch.org/mailman/listinfo/elinks-dev
