1) The action items in STATUS.html need to be addressed. The first (Review
Abstractions) is especially important, since we need to set the right
tone for Resources before it goes out into the big wide world as an
official release. IMNSHO, there is still some serious work needed here
(which I'm
Here are a few things that need to happen:
1) The action items in STATUS.html need to be addressed. The first (Review
Abstractions) is especially important, since we need to set the right
tone for Resources before it goes out into the big wide world as an
official release. IMNSHO, there is still
I agree with the comments below. I currently have my own resource management system
that has some similarities with [resources], but a lot more power.
I would like to see [resources] improved prior to a release. I may not be able to code
(due to time), but I hope I could submit ideas.
Stephen
James Mitchell wrote:
Unless I did something wrong, my search for issues on bugzilla turns up
nothing, and I'm not sure what to make of issueTrackingUrl in project.xml.
Does it mean that we should be using
http://nagoya.apache.org/scarab/servlet/scarab/ or is it something that was
just carried
Unless I did something wrong, my search for issues on bugzilla turns up
nothing, and I'm not sure what to make of issueTrackingUrl in project.xml.
Does it mean that we should be using
http://nagoya.apache.org/scarab/servlet/scarab/ or is it something that was
just carried over when someone was
