11 seemed to be a no-op 13 is done 14 is done leaving ...
2 use rat results to fix license header issues and post rat results 3 check that all recent fixes in the trunk since the branch was made have equivalent fixes in the branch 6 need to remove dependencies on snapshot plugins (rfeng 13/7) 10b ensure that the runsamples.sh script runs ok in a linux env 12 exclude samples infrastructure classes from samples javadoc 15 ensure consistency of each sample program's javadoc to point back to central instructions for running samples 16 put an overview doc into the sdo lib project's javadoc 17 add the change summary aspects of the medical scenario sample On 18/07/07, kelvin goodson <[EMAIL PROTECTED]> wrote:
I have now ported 4 or 5 fixes that had been made to the trunk but not to the branch (task 3). While we are in this pre-release phase if you could create a patch of your local workspace when working in the trunk before committing and attach it to the JIRA, then that eases the task of porting to the branch. Better still would be to apply the patch to the branch too. Now I'm going to look at the samples javadoc issues, phase 1 = tasks 11, 12, 13, 14 Regards, Kelvin. On 18/07/07, kelvin goodson < [EMAIL PROTECTED]> wrote: > > just did 4,5,7,8,9,10(a) -- still not run the linux script > so that leaves 2,3,6,11,12,13,14, and 15,16,17 (which were badly > numbered as 12,13,14 -- doh!) > > 2 use rat results to fix license header issues and post rat results > 3 check that all recent fixes in the trunk since the branch was made > have equivalent fixes in the branch > 6 need to remove dependencies on snapshot plugins (rfeng 13/7) > 10b ensure that the runsamples.sh script runs ok in a linux env > 11 fix up bad javadoc links in samples index.html > 12 exclude samples infrastructure classes from samples javadoc > 13 fix link back to tuscany site from overview.html to point to the get > involved page > 14 incorporate Haleh's suggested paragraph [1] into overview.html > 15 ensure consistency of each sample program's javadoc to point back to > central instructions for running samples > 16 put an overview doc into the sdo lib project's javadoc > 17 add the change summary aspects of the medical scenario sample > > I'm going to tackle 3 now > > Kelvin. > > On 18/07/07, kelvin goodson <[EMAIL PROTECTED]> wrote: > > > > I'm going to number off the non jira related tasks so that its easy to > > reference them > > > > I just did 1 and now plan to do 4,5,7,8,9 > > > > 1 the pom has a "provided scope" dependency on stax -- I will fix > > this as per my note to tuscany-dev > > 2 use rat results to fix license header issues and post rat results > > 3 check that all recent fixes in the trunk since the branch was made > > have equivalent fixes in the branch > > > > the following have been raised by comments on RC1 > > > > 4 NOTICE files (create separate ones for impl and bin and ensure no > > disclaimer contained) > > 5 need to update release notes with descriptive para and fixed jiras > > 6 need to remove dependencies on snapshot plugins (rfeng 13/7) > > 7 should remove EPL license from src distro > > 8 add stax reference in bin distro license > > 9 add readme to bin distro samples folder > > 10 fix up runsamples scripts to be more robust/helpful and ensure that > > the runsamples.sh script runs ok in a linux env > > 11 fix up bad javadoc links in samples index.html > > 12 exclude samples infrastructure classes from samples javadoc > > 13 fix link back to tuscany site from overview.html to point to the > > get involved page > > 14 incorporate Haleh's suggested paragraph [1] into overview.html > > > > and some of my own todos that I hope to get to > > 12 ensure consistency of each sample program's javadoc to point back > > to central instructions for running samples > > 13 put an overview doc into the sdo lib project's javadoc > > 14 add the change summary aspects of the medical scenario sample > > > > Regards, Kelvin > > > > On 17/07/07, kelvin goodson <[EMAIL PROTECTED]> wrote: > > > > > > This release is running later than I had hoped due to extra jiras > > > being added to the plan, and a few issues that have come up after recent > > > fixe, so we are a bit behind where I'd proposed we should be in terms of > > > getting this release out. Please help with some of these TODOs if you can. > > > If you plan to tackle anything please post here so that we don't overlap; > > > I'll do the same. > > > > > > these are the things that I think are "must-fix" > > > > > > 1143 -- the issues re test failures are being resolved -- david's > > > working on this > > > 1429 -- i've looked at this and it is fine apart from the casting to > > > HelperContextImpls -- i put a note on the jira, > > > 1428 -- note appended to jira asking for code to > > > exercise/demonstrate the fix > > > > > > other issues raised on the list > > > > > > the pom has a "provided scope" dependency on stax -- I will fix > > > this as per my note to tuscany-dev > > > use rat results to fix license header issues and post rat results > > > check that all recent fixes in the trunk since the branch was made > > > have equivalent fixes in the branch > > > > > > the following have been raised by comments on RC1 > > > > > > NOTICE files (create separate ones for impl and bin and ensure no > > > disclaimer contained) > > > need to update release notes with descriptive para and fixed jiras > > > need to remove dependencies on snapshot plugins (rfeng 13/7) > > > should remove EPL license from src distro > > > add stax reference in bin distro license > > > add readme to bin distro samples folder > > > fix up runsamples scripts to be more robust/helpful and ensure that > > > the runsamples.sh script runs ok in a linux env > > > fix up bad javadoc links in samples index.html > > > exclude samples infrastructure classes from samples javadoc > > > fix link back to tuscany site from overview.html to point to the get > > > involved page > > > incorporate Haleh's suggested paragraph [1] into overview.html > > > > > > and some of my own todos that I hope to get to > > > ensure consistency of each sample program's javadoc to point back to > > > central instructions for running samples > > > put an overview doc into the sdo lib project's javadoc > > > add the change summary aspects of the medical scenario sample > > > > > > > > > ==================================================== > > > > > > [1] > > > b) You could remove the first sentence since it does not really make > > > sense. > > > How about .. Apache Tuscany SDO Samples are provided here to help > > > users > > > learn SDO.'index by SDO subproject ' lists the different samples > > > available > > > to you. These samples provide a starting point for learning SDO and > > > can be > > > extended and enhanced to experiment with other available SDO > > > features. > > > Please help us enhance these samples by sending your feedback to > > > Tuscany > > > mailing list or join us and contribute to this project <get involved > > > link>. > > > > > > >
