On Mon, May 02, 2011 at 09:21:25PM +0000, corvid wrote:
Jorge wrote:
On Mon, May 02, 2011 at 02:13:19PM -0400, Benjamin Johnson wrote:
On Mon, 02 May 2011 14:06:27 -0400, corvid <corvid@lavabit.com> wrote:
Jorge wrote:
Making a new, dillo-2.3 release is not much of a point because people using dillo already have to get it from us and build it themselves, which they already do.
When fltk-1.3 is released we could make a dillo-2 final release letting users know we're going with the dillo-3 series.
Although if somebody comes with a good reason to make a dillo-2 final release now, we can make it.
It is probably nice to have a release every year or so, at least, so that wikipedia and the dillo homepage say "Dillo is alive" instead of "Dillo is dead" to visitors. Plus anyone trying to use the 2.2 release code will find that it doesn't like their libpng version.
I'm personally generally not one to follow whatever code happens to be in repositories, so for instance I thought fvwm was pretty dead -- and their recent release surprised me.
Then again, if we added a news item talking about the port being in decent shape, and added something in screenshots/ (even though it looks nearly identical to 2.2), that would be a sign of life.
I think there should be one more release of fltk-2.x Dillo, if only so the last year's worth of changes in Mercurial don't look completely abandoned. We know it's all been moved to 1.3 now, but people outside the project won't. Keep users happy, make ourselves look good...
Fair enough.
Volunteers to put up the release, make one step ahead! ;-)
This is why I was hesitant to say anything -- I knew what it was tantamount to... :)
Same here :) But seriously, we should release what we have for fltk2 in the near future. Current tip is very stable and has many improvements over our last release. Cheers, Johannes