On Jan 17, 3:27 am, Sebastien Lelong <[email protected]>
wrote:
>
> Please have a look and
> review:http://code.google.com/p/jallib/wiki/ValidationProcess
>
Greetings Seb,
Thank you for revising the document -- it is very helpful!
May review notes:
1) At the top of the document, please add that not only does this
document describe what 'files go into a release', but also 'how the
release process works'.
2) Please consider making the release process 3 steps instead of 2
steps:
1) (new step in process) announce your intention to create
a 'beta', and allow at least a few days for any discussion, last
minute updates, etc, before step 2 begins
2) create the beta, which is quite a lot of work, as you've
already documented
3) final release, as you've already documented
The new step #1 above, is keeping with your statement 'once everybody
is happy'. Otherwise, respectfully, it seems like the 'undocumented
step #1 is:'
1) At any time, anyone may feel free to create a new beta
release. And furthermore, since creating a beta is a time-consuming
process, it is essentially a defacto-new release. Only a serious
technical problem can stop a beta release from becoming an official
release.
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.
