On Jan 3, 1:13 pm, Sebastien Lelong <[email protected]> wrote: > > jallib 0.5 was available few weeks ago in group's file section for review. >
This is a confusing statement. How can it be possible? 1) The compiler in the 'release' did not exist until Dec 26, 2) your 'branch' did not occur until Dec 30. I don't see how you can release a new JALLIB that hasn't been tested with the official release of the compiler. A simple browse of the SVN online, of your 'release branch', shows sample files being modified on Dec 24th, for example. Did anyone, test anything, between Dec 26th and Dec 30th? I didn't. This 'team' made a bad mistake, but I'm not giving up. We can improve. We should improve. We must improve. One suggestion, that I made already, is to make a 'release candidate' branch or tag. Then we can test against it. And then release exactly that, and nothing new slips into the release. William ps: The key file that I updated, was TORELEASE, of course. -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
