Not having a good internet connection will create a huge backlog for messages never sent... grmbl
I also got a ping from a coworker of Al Maw where these projects went: this means there is genuine interest in them (apart from the downloads mentioned below). On 5/6/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
I also didn't see the point of why releases have to be disabled or code that compiles and at least does something has to be moved.
These particular releases imply that the code is unmaintained and left to die. If someone does download these releases and tries to get them to work with the current Wicket code base, then they are in for a nasty surprise. The code in SVN doesn't have that problem. So disabling the releases will decrease the visibility, but will also remove the idea that they are no longer maintained. [1] These projects clearly are maintained, and should be used as examples from what I hear from you. Therefore I think the best value for these projects and your effort invested in them is in having a source distribution release available for download (based on 1.3 code), and not the currently, obsolete binary release for download. I would also consider adding a small page to the wiki explaining the intent and how/what to do with the projects.
> why not take a step back and > see why we actually have these projects? At the very least they were examples that people could check out and take a look at.
I have no problem with that. But it was not clear to me, and I would guess not for other users.
It's 1.0 based as the version implies. If that isn't clear, then we could look at that further.
I would suggest disabling the downloads: they are not of any particular use at the moment, other than making the stuff visible to casual browsing users. They are dangerous in that they (the downloads) won't work with the current state of Wicket. The usage of the projects look like they are actively downloaded: [2] So let's either update these projects and release new binaries or remove the binaries and keep it in svn. I have a slight preference for the former: releases make things nice and explicit and gives people something solid to build on. Martijn [1] http://faler.wordpress.com/2007/05/28/all-the-wicket-components-you-could-ever-wish-for/ [2] http://sourceforge.net/project/stats/detail.php?group_id=134391&ugn=wicket-stuff&type=prdownload&mode=alltime&package_id=149074&release_id=0 -- Join the wicket community at irc.freenode.net: ##wicket Wicket 1.2.6 contains a very important fix. Download Wicket now! http://wicketframework.org
