Dear Les,

It isn't a problem for us to create installation package. The benefits is that
beta testers must not change very much in their scripts. Also they can downgrade
with the same ease.

During the many alphas, betas and release candidates we get some requests about
"why no package of this temporary release available".

Publishing already now as package are the fixes Ruud made. It are only fixes and
no new things. You can see it also as a kind of second final candidate of pre-
vious release. Ruud doesn't want to have the same situation between build 98 and
99, which returns as @kix value the same value.
Of course it doesn't mean we are following always all alphas and betas updates.

For us the name isn't a big issue. Site contains enough information about what
kind of release it is. Also kixtart itself shows that it is a release candidate.
Les, we were talking about "When releasing it to the public, greater care
should be exercised.". Of course we subscribe that point of view, but Ruud
explicit writes "Please feel free to share this build on your websites, but do
make sure to label it a 'Release Candidate'." and what did we do.

We have never distributed version with your qualification. We respect the
way Ruud want to distribute his program.

greetings.
_________________________
email scripting@wanadoo.nl homepage scripting@wanadoo.nl | Links | Summary of Site Site KiXforms FAQ kixtart.org library collection mirror MCA | FAQ & UDF help file UDF kixtart.org library collection mirror MCA | mirror USA | mirror europe UDF scriptlogic library collection UDFs | mirror MCA