Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
On Sunday 06 January 2002 09:18, Dan Wolfe wrote:
> Hi Tavis,
> I'm in the process of getting my feet wet with webware.
> I've came across a reference to your redesign of Webware...
>esign> and was wondering if you planned to implement this in
> version 0.7?
> The reason that I'm asking is that I have some ideas that would be
> easier to implement in the redesigned version rather than the
> current version....
> If it's not going to be in version 0.7, can you tell me what your
> plans are for it?
> - Dan
what are your ideas? I hope you don't mind that I've cc'd the devel
You can get CVS access to the experimental code at
There's a few of us working on it behind the scenes, but when/if the
actual code merge takes place is up to Chuck. Personally, I feel
that it's much easier to test the experimental code and tidy up the
few holes remaining than it would be to implement all the items on
the WishList/TodoList using the Webware 0.6 codebase. That said,
Chuck has an obligation as Webware's Benevolent Dictator to review
all the changes in the experimental code, before we merge and cut a
release. Either he has to a manual code walkthrough/review or I and
the other people working on experimental code have to make the
automated test suite comprehensive enough to mitigate the need for a
manual review by Chuck. Either way, an _official_ merge is at least
a few months away.
Chuck wants to cut an official release in Feb. I agree with him that
we should keep the official releases flowing with whatever we've got
rather than waiting for the next big thing. Whether the release in
Feb is called 0.7 is up to him.
In the meantime, I'm going to continue testing the experimental code,
encouraging people to join in on the testing, mirroring any new
additions to the official codebase, and backporting the smaller
changes in the experimental code to the official codebase wherever
Geoff has pointed out that the experimental code will only be ready
for serious consideration once we have some of the larger existing
applications running on it. With that in mind, here's what people
can do to help out:
MINIMAL EFFORT (1/2 hr)
* download the cvs version of the code
* read the README and see if what I've written makes sense.
* follow the installation instructions and report any problems
* run the automated test suite on their platform ... reporting any
problems or further documentation needed along the way
MODERATE EFFORT (a few hours to a few days)
* create a small test application, or try porting their existing
applications ... reporting any problems or further documentation
needed along the way
* add more test cases to the automated test suite. This is very easy.
EXTRA EFFORT (up to you)
* manually review the code and/or search for any TODO comments that
begin with @@.
* tackle items on the Todo/WishLists on the Wiki site or in the
experimental code's README file.
* Write documentation/howtos
There's two mailing lists set up for the experimental code: one for
reporting problems and discussing issues and another for automated
CVS notifications. http://sourceforge.net/mail/?group_id=41909
For those people who want to get their feet wet with the code, send
me a message if you want CVS write access or send patches to the
expwebware-devel email list.