On Mon, 6 Sep 1999, Randolph S. Kahle wrote:
> I am starting to work through Jacl release 1.2.4.
Help fixing bugs would be great. Just find a test case that fails and
hack away until it passes.
> I am finding bugs that I can help fix.
Yep, anyone can propose changes.
> My understanding is that this code base is "open" for people to help.
OK, here is the skinny. The 1.2 tree has been open to "big changes" for
some time now. A number of new commands were added and most of the
codebase was rewitten to support namespaces. The 1.2.4 release is still
"alpha" quality, but now that 1.2.4 is done, only bug fixes will be
applied to the 1.2 tree. The plan is to make the 1.2 tree the new
"stable" tree. My hope is that any big problems will show
themselves and the next 1.2.5 release will be "beta" quality. If anyone
wants to get bug fixes into the 1.2.5 release, they should work on them
soon because the 1.2.5 release will most likely be finished in 2 to 3
weeks. Once things settle down, and the 1.2 tree has been
"blessed by Scriptics", a new "unstable" 1.3 tree will be created.
Any changes that are not pure bug fixes would go in the 1.3 version.
As for the "proper procedure", you simply need to identify a problem
and a solution, and provide test cases that prove you solution solves
the problem without creating others. I am sure other people on the list
would be happy to post any reactions they have to your solution.
later
mo
> How are these contributions made? What is the proper procedure?
>
> Regards,
>
> Randy Kahle
----------------------------------------------------------------
The TclJava mailing list is sponsored by WebNet Technologies.
To subscribe: send mail to [EMAIL PROTECTED]
with the word SUBSCRIBE as the subject.
To unsubscribe: send mail to [EMAIL PROTECTED]
with the word UNSUBSCRIBE as the subject.
To send to the list, send email to '[EMAIL PROTECTED]'.
A list archive is at: http://www.findmail.com/listsaver/tcldallas/
