Kalle Olavi Niemitalo <[EMAIL PROTECTED]> wrote Fri, Jun 20, 2008: > Witold Filipczyk <[EMAIL PROTECTED]> writes: > > > Me and probably not only me want to package the ELinks-0.12 or even 0.13. > > If you do not want to release often, create at least monthly (or quoterly) > > snapshots, eg. elinks-0.13-080630.tar.bz2 and save them on the download > > site. Mark them as experimental.
Sounds good if somebody else is interested in starting the release process of 0.12 and master. As I have said before my ELinks time is very limited these days and mostly goes into mailing list moderation. I don't know if it would make sense to start migrating to use Google Code for hosting the downloads. I have used it for a few projects and it is quite flexible and easy to use. I think this might be preferable compared to the current download hosting that is quite complicated. Anyway, I've created a project at http://elinks.googlecode.com/ and can delete it if you think it is the wrong way to go. > I think it is time to release ELinks 0.12pre1 and 0.11.4. All > the bugs targeted for 0.12-M1 have been fixed in the elinks-0.12 > branch. I will start preparing the release of 0.11.4 in the next few days. > In master AKA 0.13.GIT, the current fix of bug 765 can easily > cause a crash. I think that should be fixed before any release > From that branch. 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. -- Jonas Fonseca _______________________________________________ elinks-dev mailing list elinks-dev@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-dev
