All this "What has been changed?" and "Where did these fixes go?" really is a general problem. I know all the information is in the CVS, but is sometimes hard to find and manage. I would propose to use some sort of logging where every non-minor change gets recorded. We use a small DTD and XSLT script that converts log entries done in XML into text/HTML output and also release notes. There are some other little features like references to the bugzilla for bug fixes. All the author of a fix/change would have to do is add a log to the XML file like in weblogs.

I would like to see this type of logging of changes in Slide 2.0. I would also merge the rudimentary logging capabilities in Slide with this one...

What do you say?

Oliver

Oliver Zeigermann wrote:
Nevermann, Dr., Peter wrote:

I have already identified the following actions, yet to be finished. I would appreciate to get an estimation of when these will be finished:

Peter:
- Clean binding and fix multistore problem, maybe enhance URI caching
- Finish ACL



I should be through, with testing and so, by end of next week (Jan-16).




Now for the showstoppers.

- Tests: look good
- Authentication wrapper: I think I fixed this, can someone confirm?



You mean SlideRealm, right? I'll try it out. BTW, I am a bit confused because inspecting CVS I noticed that nothing related to this issue changed in src/wrappers recently. Where did you check-in your fixes, Oliver?


Yes,

I could not find the reference to my post, because I accidently posted it into the users list:

http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgNo=5159


You probably did not find the change as the SlideRealm remained untouched, as changes were done to ACLSecurityImpl.


Oliver



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to