Seb,

I think we are getting closer to agreement. I'm glad.

A question: How do you go about creating the 'beta release' that is
placed into the 'group file section'?   Do you start with a fresh
'snapshot' of the whole SVN trunk?  If so, please add a SVN tag so we
know exactly what you started with.

Then, I am proposing a testing/waiting period. Participation in the
testing is voluntary.  You feel that 30 days is too long, so how about
21 days?

Now then, when we get to the end of the 21 days, and assuming we want
to make this release 'official', the question comes up-- do we release
exactly the same files as the 'beta release', or do we get a new
snapshot from trunk, and generate a new SVN tag?

My recommendation is that we go with the exact files from the 'beta
release', and provide a description of any 'known issues' that may
have been detected during the testing period.

If a major event, such as a new compiler release, were to happen
during the 21 day waiting period, this would, in my opinion, certainly
be grounds to re-start the process from the beginning.

William

--

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.


Reply via email to