Forum .LRN Q&A: Re: .LRN 2.1 a2 tagged
Can you please post a bug with steps to reproduce the WebDAV bug you describe? I can't reproduce it, and I don't see where it could be coming from. If you need to discuss it please start a new thread.
Those have been covered.
Dario, what we need to do is get you highly integrated with Sloan and Galileo so you can be part of the process (finding bugs, reporting bugs, actually using the alpha code against your data) so we can all work together. Sloan and Galileo have found that extremely productive.
How do you do your development and testing? Are you set up on the oacs-5-1 branch or on the dotlrn-2.1.0a2 tag? Do you have commit rights to commit the bugs you find and fix.
I don't know what this means.
But what is far easier is to report the bugs in the bug tracker: http://openacs.org/bugtracker/openacs
and then make a summary list of Bug name/Bug ID of things that are needed.
The bug tracker has the tracking capability for us to see if it is fixed, comment on it, etc. If it is in the forums, it is likely to get lost.
We also want to work with you.
Our plans are the following ones:
-The day September 1 checkout of CVS branch oacs-5-1 because some more solved errors that dotlrn-2-1-0a2
We have a copy of this code and are personalizing it, the day 15 September start with .LRN in production (http://pizarra.uv.es) with 200 professors, 15.000 students and 1.000 classes more or less, because with 40.000 students have problems of scalability.
I daily check the changes in the branch oacs-5-1 of the CVS, I prove them in my installation of tests (pizarra3.uv.es), and if they go well intent to put them in the production installation.
-We have user in the CVS (darior) and we go solving the errors directly in the CVS branch oacs-5-1