Re: [elinks-dev] Monthly snapshots
Kalle Olavi Niemitalo <[EMAIL PROTECTED]> wrote Fri, Jun 20, 2008: > Kalle Olavi Niemitalo <[EMAIL PROTECTED]> writes: > > > I would much rather pay for hosting elsewhere. > > By the way, do you have any statistics on the disk and network > usage at elinks.cz? In elinks.cz/download/ du -sh says 126M of which old/ has 21M. No idea about the network usage. -- Jonas Fonseca ___ elinks-dev mailing list elinks-dev@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-dev
Re: [elinks-dev] Monthly snapshots
Kalle Olavi Niemitalo <[EMAIL PROTECTED]> wrote Fri, Jun 20, 2008: > Jonas Fonseca <[EMAIL PROTECTED]> writes: > > > 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. OK, fair enough. Maybe it isn't necessary to pay for hosting, the problem with the current hosting is that we only have one account on the server, which makes things slightly less flexible. We could set up yet another rsync cronjob to populate the download directory from somewhere on the host of the master repository if pasky doesn't mind. > > 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? I was just curious from experiences a few years back where there probably was a bit more restructuring than what is the case today. If there are no real incompatibilities it sounds like you have done a really a good job. And it is nice to see that NEWS is populated with all this information. -- Jonas Fonseca ___ elinks-dev mailing list elinks-dev@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-dev
Re: [elinks-dev] Monthly snapshots
Kalle Olavi Niemitalo <[EMAIL PROTECTED]> writes: > I would much rather pay for hosting elsewhere. By the way, do you have any statistics on the disk and network usage at elinks.cz? pgpmYBB4vqdY8.pgp Description: PGP signature ___ elinks-dev mailing list elinks-dev@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-dev
Re: [elinks-dev] Monthly snapshots
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 elinks-dev@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-dev
Re: [elinks-dev] Monthly snapshots
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
Re: [elinks-dev] Monthly snapshots
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. 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. 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. pgp8XI65DEj0J.pgp Description: PGP signature ___ elinks-dev mailing list elinks-dev@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-dev
