Ralf, that's not really an option as most likely (though I am not 100% sure) after applying the first (and the second one), it will (again hopefully) not be necessary to apply the last one any more. In other words, I want the additional user testing before embarking to address the remaining issue(s).
Werner Ralf Joachim wrote: > Hi Werner, > > I am not sure if it realy makes sense to create a snapshot after every > patch. I suggest to apply all 3 small patches, create one snapshot > including all changes and see what happens, > > Regards > Ralf > > > Werner Guttmann schrieb: >> Hi, >> >> for those of you waiting for issues CASTOR-1986, CASTOR-1934, >> CASTOR-1864 et alias to be resolved, let me just mention that I am about >> start committing patches for CASTOR-1986. As this is about smallish >> regression issues with the new descriptor package for descriptor classes >> generated as part of XML code generation, I am trying to be extra >> careful (hence my somewhat slowish progress with these issues). >> >> I will make new snapshot releases available after each individual commit >> set, and would appreciate as much feedback as possible after each commit >> (with each new snapshot release). >> >> For those of you that are not 100% familiar with snapshot releases and >> their significance, let me just re-iterate that a snapshot release is a >> controlled release of SVN trunk that happens to be ... >> >> - in binary form >> - is uploaded to the Codehaus snapshot repository >> - receives the same level of testing as a 'normal' release. >> >> The difference is that we - upon release of a snapshot - we don't update >> HTML docs, Javadocs, etc. >> >> Regards >> Werner >> >> >> --------------------------------------------------------------------- >> To unsubscribe from this list please visit: >> >> http://xircles.codehaus.org/manage_email > --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
