Got the commit message. Thanks ... Will keep in mind about committing per issue. I resolved the issues in Jira too.
Manoj On Wed, Jun 10, 2009 at 10:02 PM, scott comer <[email protected]> wrote: > thanks. you should see your commit message now. i had to approve you > sending a message to that > list (subscribe! mailto:[email protected] < > [email protected]>). > > one other point. try to limit each commit to a single topic (bug fix, > etc.). > > if you didn't mark the bugs as resolved in jira, please do that. i will > update > and verify in the morning and roll a new release. whee! > > > scott out > > Manoj Ganesan wrote: > >> I have checked in the fix for ETCH-76 and ETCH-77. I haven't received any >> commit messages via email as yet, don't know what's the delay in that. >> Manoj >> >> >> On Wed, Jun 10, 2009 at 8:16 PM, scott comer <[email protected]> wrote: >> >> >> >>> i marked the bugs fix for 1.1 and assigned them to you. i also taught >>> jira >>> that you're a committer >>> now. >>> >>> when you commit make sure the commit comment calls out the bug you're >>> fixing. i've been using >>> this pattern. the bug id (case sensitive) and the summary. that's really >>> all you need to say unless >>> you feel like being chatty. >>> >>> "fix for ETCH-77: Incompatibility in the READMEs for the bundled >>> examples" >>> >>> if you use that form, the subversion commit process will attach >>> information >>> to the bug >>> in jira which is cool. >>> >>> thanks, >>> scott out >>> >>> Manoj Ganesan wrote: >>> >>> >>> >>>> The fix goes into trunk right? Or is there another branch for the >>>> release >>>> where I should check in the change? Also, should I put in the fix for >>>> http://issues.apache.org/jira/browse/ETCH-76 as well? >>>> Manoj >>>> >>>> >>>> On Wed, Jun 10, 2009 at 6:56 PM, scott comer <[email protected]> wrote: >>>> >>>> >>>> >>>> >>>> >>>>> i agree. manoj, you wanna do the honors? >>>>> >>>>> scott out >>>>> >>>>> >>>>> James Dixson wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>>> that should probably be fixed before the release. Good catch Manoj. >>>>>> >>>>>> >>>>>> -- >>>>>> james >>>>>> >>>>>> On Jun 10, 2009, at 2:35 PM, Manoj Ganesan wrote: >>>>>> >>>>>> There seems to be an incompatibility in the READMEs for the bundled >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>> examples. The ant scripts for running the examples have been updated >>>>>>> with >>>>>>> the apache standards (i.e., appending org.apache before our package >>>>>>> conventions) but the READMEs haven't. So, even though the builds >>>>>>> complete >>>>>>> fine, anyone who reads the README and tries to run any of these >>>>>>> examples >>>>>>> would run into an error. Basically, these READMEs need to be updated >>>>>>> with >>>>>>> the naming convention. >>>>>>> >>>>>>> Manoj >>>>>>> >>>>>>> >>>>>>> On Wed, Jun 10, 2009 at 11:09 AM, scott comer <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>> +1 >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>>> checked signatures and hashes >>>>>>>> download source and build on unix >>>>>>>> download source and build on windows >>>>>>>> download windows exe installer and build examples >>>>>>>> checked rat report >>>>>>>> >>>>>>>> scott out >>>>>>>> >>>>>>>> >>>>>>>> scott comer wrote: >>>>>>>> >>>>>>>> The release artifacts are here: >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> http://people.apache.org/~sccomer/apache-etch-1.1.0-incubating/< >>>>>>>>> http://people.apache.org/%7Esccomer/apache-etch-1.1.0-incubating/> >>>>>>>>> >>>>>>>>> i corrected the name of the directory in the -src.tar.gz to remove >>>>>>>>> the >>>>>>>>> -rc2 qualifier. >>>>>>>>> >>>>>>>>> i also corrected the names of the source artifacts to be -src >>>>>>>>> instead >>>>>>>>> of >>>>>>>>> -source. >>>>>>>>> >>>>>>>>> i renamed the release tag to release-1.1.0-incubating. >>>>>>>>> >>>>>>>>> scott out >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>> >>> >>> >> >> >> > >
