[dbutils] Release process for dbutils-1.1. How can I help?
Henri Yandell wrote: So unless any of the non-versioned issues seem like they should go in, it's time to start the fun of the release process. Hen Should I prepare a summary of the non-versioned issues? What else can I do to push the release process? Alan Canon
Re: [dbutils] Release process for dbutils-1.1. How can I help?
On 11/7/06, Alan Canon [EMAIL PROTECTED] wrote: Henri Yandell wrote: So unless any of the non-versioned issues seem like they should go in, it's time to start the fun of the release process. Hen Should I prepare a summary of the non-versioned issues? Only if you think any should go in 1.1. What else can I do to push the release process? I did some work on it at the weekend - fixed the code to build under 1.3. I'm working on the changes.xml file (release notes), I'll have that finished today. Other things that jump to mind: * We should create a pom.xml file (Maven-2 build). As long as the parent gets deployed (cf: some other thread on commons-dev). Feel free to take a stab at that - shouldn't be too hard as there are other pom.xml's to (largely) copy. * Update the site - this mostly means changing 1.0 for 1.1 if it appears in the text, but any problems you can find/patch in the site are good for now. * Create a jardiff report - need to see what's changed API-wise and add that to release notes. * Build the ant dist and maven site and call a vote. I'll take care of that once the other bits are done. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dbutils] Release process for dbutils-1.1. How can I help?
On 11/7/06, Henri Yandell [EMAIL PROTECTED] wrote: On 11/7/06, Alan Canon [EMAIL PROTECTED] wrote: Henri Yandell wrote: So unless any of the non-versioned issues seem like they should go in, it's time to start the fun of the release process. Hen Should I prepare a summary of the non-versioned issues? Only if you think any should go in 1.1. What else can I do to push the release process? I did some work on it at the weekend - fixed the code to build under 1.3. I'm working on the changes.xml file (release notes), I'll have that finished today. Other things that jump to mind: * We should create a pom.xml file (Maven-2 build). As long as the parent gets deployed (cf: some other thread on commons-dev). Feel free to take a stab at that - shouldn't be too hard as there are other pom.xml's to (largely) copy. * Update the site - this mostly means changing 1.0 for 1.1 if it appears in the text, but any problems you can find/patch in the site are good for now. * Create a jardiff report - need to see what's changed API-wise and add that to release notes. http://people.apache.org/~bayard/dbutils-1.0-to-1.1-jardiff.html It doesn't look that bad - jardiff complains that we've moved a method into a superclass in a few places. So a recompile will be needed (I think) rather than being able to drop the jar in place. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dbutils] Release process for dbutils-1.1. How can I help?
Henri Yandell wrote: http://people.apache.org/~bayard/dbutils-1.0-to-1.1-jardiff.html It doesn't look that bad - jardiff complains that we've moved a method into a superclass in a few places. So a recompile will be needed (I think) rather than being able to drop the jar in place. You might want to try a clirr report to check for binary compatability. IIRC, moving a method up the hierarchy is binary compatible. If not, then a simple super.xxx() method in the subclasses where the method was removed from should be added. Stephen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dbutils] Release process for dbutils-1.1. How can I help?
On 11/7/06, Stephen Colebourne [EMAIL PROTECTED] wrote: Henri Yandell wrote: http://people.apache.org/~bayard/dbutils-1.0-to-1.1-jardiff.html It doesn't look that bad - jardiff complains that we've moved a method into a superclass in a few places. So a recompile will be needed (I think) rather than being able to drop the jar in place. You might want to try a clirr report to check for binary compatability. IIRC, moving a method up the hierarchy is binary compatible. It seems to give the same info: http://people.apache.org/~bayard/dbutils-1.0-to-1.1-clirr.txt If not, then a simple super.xxx() method in the subclasses where the method was removed from should be added. Yup, that'd work. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dbutils] Release process for dbutils-1.1. How can I help?
On 11/7/06, Henri Yandell [EMAIL PROTECTED] wrote: On 11/7/06, Stephen Colebourne [EMAIL PROTECTED] wrote: Henri Yandell wrote: http://people.apache.org/~bayard/dbutils-1.0-to-1.1-jardiff.html It doesn't look that bad - jardiff complains that we've moved a method into a superclass in a few places. So a recompile will be needed (I think) rather than being able to drop the jar in place. You might want to try a clirr report to check for binary compatability. IIRC, moving a method up the hierarchy is binary compatible. It seems to give the same info: http://people.apache.org/~bayard/dbutils-1.0-to-1.1-clirr.txt snip/ INFOs are OK though. -Rahul If not, then a simple super.xxx() method in the subclasses where the method was removed from should be added. Yup, that'd work. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dbutils] Release process for dbutils-1.1. How can I help?
On 11/7/06, Rahul Akolkar [EMAIL PROTECTED] wrote: On 11/7/06, Henri Yandell [EMAIL PROTECTED] wrote: On 11/7/06, Stephen Colebourne [EMAIL PROTECTED] wrote: Henri Yandell wrote: http://people.apache.org/~bayard/dbutils-1.0-to-1.1-jardiff.html It doesn't look that bad - jardiff complains that we've moved a method into a superclass in a few places. So a recompile will be needed (I think) rather than being able to drop the jar in place. You might want to try a clirr report to check for binary compatability. IIRC, moving a method up the hierarchy is binary compatible. It seems to give the same info: http://people.apache.org/~bayard/dbutils-1.0-to-1.1-clirr.txt snip/ INFOs are OK though. Yep, you're both right. Quick test shows that in 1.3 and 1.5 the JVM happily switches to the parent method of 1.1 if compiled against the child method in 1.0. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
