Hans~
I am interested in finding ways to help. What would be required? I imagine something like:
- getting an automatic email after the nightly tests.
- Logging into the svn or whatever your versioning system is (would have to
be trained on this part). 3. Downloading the said help patches. 4. Testing said help patches on local machine. 5. If fix is found, upload new file to svn and add relevant comments to versioning system (training again) .
If you could come up with a very straightforward, idiot-proof checklist of actions, I could likely offer an hour or two a week on this task. My only machine right now is running OS X 10.5.6, so that's the scope of my usefulness to the project.
~Kyle
On Fri, Feb 27, 2009 at 12:19 PM, Hans-Christoph Steiner hans@eds.orgwrote:
Hey all,
A while back, I wrote some scripts that can automatically load every help patch and load every objectclass. I would like to set these up to run every night, but I don't think I'll be able to keep up with the output from this, i.e. fixing the help patches that crash and at the same manage getting this Pd-extended 0.41 release finished. So I want to see if there is anyone willing to handle this whole process.
I think it will make Pd much more reliable if we can track down the little errors in help patches that can cause crashes. As far as I am concerned it can be managed how ever anyone wants to do it. I have these basic scripts ready to go, but they could easily be replaced with something else, if anyone else wants to do that.
I think this could then be expanded into a broader testing framework.
.hc
'You people have such restrictive dress for women,’ she said, hobbling away in three inch heels and panty hose to finish out another pink- collar temp pool day. - “Hijab Scene #2", by Mohja Kahf
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list