Mike, I did not get a chance to review your changes last night, I am sorry. I will do it tonight.
> Still, I'd like to see these changes included in some > near-term release > (assuming they are accepted) because I have some ideas about other > things that I've seen along the way (like the > under-utilization of the > o.a.l.helpers.Loader utility class), but I'd like to get one set of > changes off my plate before I start harassing the list with a new set. I have been assuming that the 1.2 branch is for bug fixes only. So, new features or radical changes would go into the main branch. 1.3 is roughly slated for release at the end of the year. I should take the same tack as you, finishing one idea before coming up with the next one...:-) > While we're at it, is the 1.3 code available via CVS for us > less-privileged submitters? And, where is the 1.2.5 code in > CVS. I can > get the source in the download, but I don't have anywhere in the > repository to compare with any subsequent changes I might make. The latest 1.2 code is on a cvs branch named "v1_2-branch". When you check out using cvs, you can use that tag/branch name. The next major release (1.3) is on the "main" branch, and does not require a tag/branch name when checking out the files. Ceki, when you release each version, how do you tag the cvs repository? > [ego stroking comments erased] :-) -Mark -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
