Re: svn commit: r578422 - /ofbiz/branches/release4.0/fra
Locked
Re: svn commit: r578422 - /ofbiz/branches/release4.0/fra
 
|
This change probably won't have any effect in the branch as the service semaphore stuff was only added a couple of weeks ago, long after the branch was done, and it's a new feature in the framework that shouldn't go into the branch. Using it in the branch shouldn't cause things to not function, but there will be a XML validation error every time the file is read. -David [hidden email] wrote: > Author: jleroux > Date: Sat Sep 22 05:50:10 2007 > New Revision: 578422 > > URL: http://svn.apache.org/viewvc?rev=578422&view=rev > Log: > Applied fix from trunk for revision: 577097 > > Modified: > ofbiz/branches/release4.0/framework/service/servicedef/services.xml > > Modified: ofbiz/branches/release4.0/framework/service/servicedef/services.xml > URL: http://svn.apache.org/viewvc/ofbiz/branches/release4.0/framework/service/servicedef/services.xml?rev=578422&r1=578421&r2=578422&view=diff > ============================================================================== > --- ofbiz/branches/release4.0/framework/service/servicedef/services.xml (original) > +++ ofbiz/branches/release4.0/framework/service/servicedef/services.xml Sat Sep 22 05:50:10 2007 > @@ -26,7 +26,7 @@ > > <!-- Service Engine Services --> > <service name="purgeOldJobs" engine="java" > - location="org.ofbiz.service.ServiceUtil" invoke="purgeOldJobs" auth="true" use-transaction="false"> > + location="org.ofbiz.service.ServiceUtil" invoke="purgeOldJobs" auth="true" use-transaction="false" semaphore="wait"> > <description>Cleans out old jobs which have been around longer then what is defined in serviceengine.xml</description> > <required-permissions join-type="AND"> > <check-permission permission="SERVICE_INVOKE_ANY"/> > > |
Re: svn commit: r578422 - /ofbiz/branches/release4.0/fra
Administrator
|
David,
Sorry, I will revert. I will now update the release when I'm absolutly sure that it must be done and have not been. Actually changes are more and more hard to merge anyway. And I guess soon a binary release could be done. Jacques ----- Message d'origine ----- De : "David E Jones" <[hidden email]> À : <[hidden email]> Cc : <[hidden email]> Envoyé : jeudi 27 septembre 2007 17:30 Objet : Re: svn commit: r578422 - /ofbiz/branches/release4.0/framework/service/servicedef/services.xml > > This change probably won't have any effect in the branch as the service semaphore stuff was only added a couple of weeks ago, long after the branch was done, and it's a new feature in the framework that shouldn't go into the branch. > > Using it in the branch shouldn't cause things to not function, but there will be a XML validation error every time the file is read. > > -David > > > [hidden email] wrote: > > Author: jleroux > > Date: Sat Sep 22 05:50:10 2007 > > New Revision: 578422 > > > > URL: http://svn.apache.org/viewvc?rev=578422&view=rev > > Log: > > Applied fix from trunk for revision: 577097 > > > > Modified: > > ofbiz/branches/release4.0/framework/service/servicedef/services.xml > > > > Modified: ofbiz/branches/release4.0/framework/service/servicedef/services.xml > > URL: > > ============================================================================== > > --- ofbiz/branches/release4.0/framework/service/servicedef/services.xml (original) > > +++ ofbiz/branches/release4.0/framework/service/servicedef/services.xml Sat Sep 22 05:50:10 2007 > > @@ -26,7 +26,7 @@ > > > > <!-- Service Engine Services --> > > <service name="purgeOldJobs" engine="java" > > - location="org.ofbiz.service.ServiceUtil" invoke="purgeOldJobs" auth="true" use-transaction="false"> > > + location="org.ofbiz.service.ServiceUtil" invoke="purgeOldJobs" auth="true" use-transaction="false" semaphore="wait"> > > <description>Cleans out old jobs which have been around longer then what is defined in serviceengine.xml</description> > > <required-permissions join-type="AND"> > > <check-permission permission="SERVICE_INVOKE_ANY"/> > > > > > |
|
|
The release branch will need someone very familiar with it, someone who can assess incoming
patches, massage them if necessary, and then merge them into the branch. Should be easier if we stick to only bugfixes. For every incoming bugfix, try to reproduce bug in release branch first. Understand the bug, the bugfix, make sure the bugfix does fix the bug, then apply it. Jonathon Jacques Le Roux wrote: > David, > > Sorry, I will revert. I will now update the release when I'm absolutly sure that it must be done and have not been. Actually changes > are more and more hard to merge anyway. And I guess soon a binary release could be done. > > Jacques > > ----- Message d'origine ----- > De : "David E Jones" <[hidden email]> > À : <[hidden email]> > Cc : <[hidden email]> > Envoyé : jeudi 27 septembre 2007 17:30 > Objet : Re: svn commit: r578422 - /ofbiz/branches/release4.0/framework/service/servicedef/services.xml > > >> This change probably won't have any effect in the branch as the service semaphore stuff was only added a couple of weeks ago, long > after the branch was done, and it's a new feature in the framework that shouldn't go into the branch. >> Using it in the branch shouldn't cause things to not function, but there will be a XML validation error every time the file is > read. >> -David >> >> >> [hidden email] wrote: >>> Author: jleroux >>> Date: Sat Sep 22 05:50:10 2007 >>> New Revision: 578422 >>> >>> URL: http://svn.apache.org/viewvc?rev=578422&view=rev >>> Log: >>> Applied fix from trunk for revision: 577097 >>> >>> Modified: >>> ofbiz/branches/release4.0/framework/service/servicedef/services.xml >>> >>> Modified: ofbiz/branches/release4.0/framework/service/servicedef/services.xml >>> URL: > http://svn.apache.org/viewvc/ofbiz/branches/release4.0/framework/service/servicedef/services.xml?rev=578422&r1=578421&r2=578422&view=diff >>> ============================================================================== >>> --- ofbiz/branches/release4.0/framework/service/servicedef/services.xml (original) >>> +++ ofbiz/branches/release4.0/framework/service/servicedef/services.xml Sat Sep 22 05:50:10 2007 >>> @@ -26,7 +26,7 @@ >>> >>> <!-- Service Engine Services --> >>> <service name="purgeOldJobs" engine="java" >>> - location="org.ofbiz.service.ServiceUtil" invoke="purgeOldJobs" auth="true" use-transaction="false"> >>> + location="org.ofbiz.service.ServiceUtil" invoke="purgeOldJobs" auth="true" use-transaction="false" > semaphore="wait"> >>> <description>Cleans out old jobs which have been around longer then what is defined in serviceengine.xml</description> >>> <required-permissions join-type="AND"> >>> <check-permission permission="SERVICE_INVOKE_ANY"/> >>> >>> > > |
Re: svn commit: r578422 - /ofbiz/branches/release4.0/fra
|
Administrator
|
Yes, I agree but who has really the time to do that ? But don't worry, I back ported must of the fixes carefully.
Jacques De : "Jonathon -- Improov" <[hidden email]> > The release branch will need someone very familiar with it, someone who can assess incoming > patches, massage them if necessary, and then merge them into the branch. > > Should be easier if we stick to only bugfixes. For every incoming bugfix, try to reproduce bug in > release branch first. Understand the bug, the bugfix, make sure the bugfix does fix the bug, then > apply it. > > Jonathon > > Jacques Le Roux wrote: > > David, > > > > Sorry, I will revert. I will now update the release when I'm absolutly sure that it must be done and have not been. Actually > > are more and more hard to merge anyway. And I guess soon a binary release could be done. > > > > Jacques > > > > ----- Message d'origine ----- > > De : "David E Jones" <[hidden email]> > > À : <[hidden email]> > > Cc : <[hidden email]> > > Envoyé : jeudi 27 septembre 2007 17:30 > > Objet : Re: svn commit: r578422 - /ofbiz/branches/release4.0/framework/service/servicedef/services.xml > > > > > >> This change probably won't have any effect in the branch as the service semaphore stuff was only added a couple of weeks ago, > > after the branch was done, and it's a new feature in the framework that shouldn't go into the branch. > >> Using it in the branch shouldn't cause things to not function, but there will be a XML validation error every time the file is > > read. > >> -David > >> > >> > >> [hidden email] wrote: > >>> Author: jleroux > >>> Date: Sat Sep 22 05:50:10 2007 > >>> New Revision: 578422 > >>> > >>> URL: http://svn.apache.org/viewvc?rev=578422&view=rev > >>> Log: > >>> Applied fix from trunk for revision: 577097 > >>> > >>> Modified: > >>> ofbiz/branches/release4.0/framework/service/servicedef/services.xml > >>> > >>> Modified: ofbiz/branches/release4.0/framework/service/servicedef/services.xml > >>> URL: > > > >>> ============================================================================== > >>> --- ofbiz/branches/release4.0/framework/service/servicedef/services.xml (original) > >>> +++ ofbiz/branches/release4.0/framework/service/servicedef/services.xml Sat Sep 22 05:50:10 2007 > >>> @@ -26,7 +26,7 @@ > >>> > >>> <!-- Service Engine Services --> > >>> <service name="purgeOldJobs" engine="java" > >>> - location="org.ofbiz.service.ServiceUtil" invoke="purgeOldJobs" auth="true" use-transaction="false"> > >>> + location="org.ofbiz.service.ServiceUtil" invoke="purgeOldJobs" auth="true" use-transaction="false" > > semaphore="wait"> > >>> <description>Cleans out old jobs which have been around longer then what is defined in serviceengine.xml</description> > >>> <required-permissions join-type="AND"> > >>> <check-permission permission="SERVICE_INVOKE_ANY"/> > >>> > >>> > > > > > |
Re: svn commit: r578422 - /ofbiz/branches/release4.0/fra
|
|
And there are people watching to complain about possible problems with such... but like Jacques says that's all we have resources for now (and even that's a stretch with so little volunteer effort and feedback on the branch...). -David Jacques Le Roux wrote: > Yes, I agree but who has really the time to do that ? But don't worry, I back ported must of the fixes carefully. > > Jacques > > De : "Jonathon -- Improov" <[hidden email]> >> The release branch will need someone very familiar with it, someone who can assess incoming >> patches, massage them if necessary, and then merge them into the branch. >> >> Should be easier if we stick to only bugfixes. For every incoming bugfix, try to reproduce bug in >> release branch first. Understand the bug, the bugfix, make sure the bugfix does fix the bug, then >> apply it. >> >> Jonathon >> >> Jacques Le Roux wrote: >>> David, >>> >>> Sorry, I will revert. I will now update the release when I'm absolutly sure that it must be done and have not been. Actually > changes >>> are more and more hard to merge anyway. And I guess soon a binary release could be done. >>> >>> Jacques >>> >>> ----- Message d'origine ----- >>> De : "David E Jones" <[hidden email]> >>> À : <[hidden email]> >>> Cc : <[hidden email]> >>> Envoyé : jeudi 27 septembre 2007 17:30 >>> Objet : Re: svn commit: r578422 - /ofbiz/branches/release4.0/framework/service/servicedef/services.xml >>> >>> >>>> This change probably won't have any effect in the branch as the service semaphore stuff was only added a couple of weeks ago, > long >>> after the branch was done, and it's a new feature in the framework that shouldn't go into the branch. >>>> Using it in the branch shouldn't cause things to not function, but there will be a XML validation error every time the file is >>> read. >>>> -David >>>> >>>> >>>> [hidden email] wrote: >>>>> Author: jleroux >>>>> Date: Sat Sep 22 05:50:10 2007 >>>>> New Revision: 578422 >>>>> >>>>> URL: http://svn.apache.org/viewvc?rev=578422&view=rev >>>>> Log: >>>>> Applied fix from trunk for revision: 577097 >>>>> >>>>> Modified: >>>>> ofbiz/branches/release4.0/framework/service/servicedef/services.xml >>>>> >>>>> Modified: ofbiz/branches/release4.0/framework/service/servicedef/services.xml >>>>> URL: > http://svn.apache.org/viewvc/ofbiz/branches/release4.0/framework/service/servicedef/services.xml?rev=578422&r1=578421&r2=578422&view=diff >>>>> ============================================================================== >>>>> --- ofbiz/branches/release4.0/framework/service/servicedef/services.xml (original) >>>>> +++ ofbiz/branches/release4.0/framework/service/servicedef/services.xml Sat Sep 22 05:50:10 2007 >>>>> @@ -26,7 +26,7 @@ >>>>> >>>>> <!-- Service Engine Services --> >>>>> <service name="purgeOldJobs" engine="java" >>>>> - location="org.ofbiz.service.ServiceUtil" invoke="purgeOldJobs" auth="true" use-transaction="false"> >>>>> + location="org.ofbiz.service.ServiceUtil" invoke="purgeOldJobs" auth="true" use-transaction="false" >>> semaphore="wait"> >>>>> <description>Cleans out old jobs which have been around longer then what is defined in serviceengine.xml</description> >>>>> <required-permissions join-type="AND"> >>>>> <check-permission permission="SERVICE_INVOKE_ANY"/> >>>>> >>>>> >>> > |
|
|
> so little volunteer effort and feedback on the branch
Hmm. Maybe there could be early binaries (alphas) for download, so people won't have to go to SVN to grab it? I've been trying to document "above-the-framework" stuff in OFBiz. I think I'll keep to the release branch. Question is, if I start churning out lots of docs (and "complaints") about the release branch, will it move forward faster? I don't want my docs to be stuck to a 1-year-old release. Preferably, there should be quarterly releases, with each major release bringing in new features. Yeah, that means we need tons of feedback to stabilize each release inside of 3 months. Jonathon David E Jones wrote: > > And there are people watching to complain about possible problems with > such... but like Jacques says that's all we have resources for now (and > even that's a stretch with so little volunteer effort and feedback on > the branch...). > > -David > > > Jacques Le Roux wrote: >> Yes, I agree but who has really the time to do that ? But don't worry, >> I back ported must of the fixes carefully. >> >> Jacques >> >> De : "Jonathon -- Improov" <[hidden email]> >>> The release branch will need someone very familiar with it, someone >>> who can assess incoming >>> patches, massage them if necessary, and then merge them into the branch. >>> >>> Should be easier if we stick to only bugfixes. For every incoming >>> bugfix, try to reproduce bug in >>> release branch first. Understand the bug, the bugfix, make sure the >>> bugfix does fix the bug, then >>> apply it. >>> >>> Jonathon >>> >>> Jacques Le Roux wrote: >>>> David, >>>> >>>> Sorry, I will revert. I will now update the release when I'm >>>> absolutly sure that it must be done and have not been. Actually >> changes >>>> are more and more hard to merge anyway. And I guess soon a binary >>>> release could be done. >>>> >>>> Jacques >>>> >>>> ----- Message d'origine ----- De : "David E Jones" >>>> <[hidden email]> >>>> À : <[hidden email]> >>>> Cc : <[hidden email]> >>>> Envoyé : jeudi 27 septembre 2007 17:30 >>>> Objet : Re: svn commit: r578422 - >>>> /ofbiz/branches/release4.0/framework/service/servicedef/services.xml >>>> >>>> >>>>> This change probably won't have any effect in the branch as the >>>>> service semaphore stuff was only added a couple of weeks ago, >> long >>>> after the branch was done, and it's a new feature in the framework >>>> that shouldn't go into the branch. >>>>> Using it in the branch shouldn't cause things to not function, but >>>>> there will be a XML validation error every time the file is >>>> read. >>>>> -David >>>>> >>>>> >>>>> [hidden email] wrote: >>>>>> Author: jleroux >>>>>> Date: Sat Sep 22 05:50:10 2007 >>>>>> New Revision: 578422 >>>>>> >>>>>> URL: http://svn.apache.org/viewvc?rev=578422&view=rev >>>>>> Log: >>>>>> Applied fix from trunk for revision: 577097 >>>>>> >>>>>> Modified: >>>>>> >>>>>> ofbiz/branches/release4.0/framework/service/servicedef/services.xml >>>>>> >>>>>> Modified: >>>>>> ofbiz/branches/release4.0/framework/service/servicedef/services.xml >>>>>> URL: >> http://svn.apache.org/viewvc/ofbiz/branches/release4.0/framework/service/servicedef/services.xml?rev=578422&r1=578421&r2=578422&view=diff >> >>>>>> ============================================================================== >>>>>> >>>>>> --- >>>>>> ofbiz/branches/release4.0/framework/service/servicedef/services.xml >>>>>> (original) >>>>>> +++ >>>>>> ofbiz/branches/release4.0/framework/service/servicedef/services.xml >>>>>> Sat Sep 22 05:50:10 2007 >>>>>> @@ -26,7 +26,7 @@ >>>>>> >>>>>> <!-- Service Engine Services --> >>>>>> <service name="purgeOldJobs" engine="java" >>>>>> - location="org.ofbiz.service.ServiceUtil" >>>>>> invoke="purgeOldJobs" auth="true" use-transaction="false"> >>>>>> + location="org.ofbiz.service.ServiceUtil" >>>>>> invoke="purgeOldJobs" auth="true" use-transaction="false" >>>> semaphore="wait"> >>>>>> <description>Cleans out old jobs which have been around longer >>>>>> then what is defined in serviceengine.xml</description> >>>>>> <required-permissions join-type="AND"> >>>>>> <check-permission permission="SERVICE_INVOKE_ANY"/> >>>>>> >>>>>> >>>> >> > > |
Re: svn commit: r578422 - /ofbiz/branches/release4.0/fra
|
Administrator
|
Jonathon,
Due to lack of HR I guess you should still refer to http://docs.ofbiz.org/display/OFBADMIN/Release+Plan#ReleasePlan-GeneralReleasePolicies Jacques ----- Message d'origine ----- De : "Jonathon -- Improov" <[hidden email]> À : <[hidden email]> Envoyé : vendredi 28 septembre 2007 04:08 Objet : Re: svn commit: r578422 - /ofbiz/branches/release4.0/framework/service/servicedef/services.xml > > so little volunteer effort and feedback on the branch > > Hmm. Maybe there could be early binaries (alphas) for download, so people won't have to go to SVN > to grab it? > > I've been trying to document "above-the-framework" stuff in OFBiz. I think I'll keep to the > release branch. > > Question is, if I start churning out lots of docs (and "complaints") about the release branch, > will it move forward faster? I don't want my docs to be stuck to a 1-year-old release. Preferably, > there should be quarterly releases, with each major release bringing in new features. Yeah, that > means we need tons of feedback to stabilize each release inside of 3 months. > > Jonathon > > David E Jones wrote: > > > > And there are people watching to complain about possible problems with > > such... but like Jacques says that's all we have resources for now (and > > even that's a stretch with so little volunteer effort and feedback on > > the branch...). > > > > -David > > > > > > Jacques Le Roux wrote: > >> Yes, I agree but who has really the time to do that ? But don't worry, > >> I back ported must of the fixes carefully. > >> > >> Jacques > >> > >> De : "Jonathon -- Improov" <[hidden email]> > >>> The release branch will need someone very familiar with it, someone > >>> who can assess incoming > >>> patches, massage them if necessary, and then merge them into the branch. > >>> > >>> Should be easier if we stick to only bugfixes. For every incoming > >>> bugfix, try to reproduce bug in > >>> release branch first. Understand the bug, the bugfix, make sure the > >>> bugfix does fix the bug, then > >>> apply it. > >>> > >>> Jonathon > >>> > >>> Jacques Le Roux wrote: > >>>> David, > >>>> > >>>> Sorry, I will revert. I will now update the release when I'm > >>>> absolutly sure that it must be done and have not been. Actually > >> changes > >>>> are more and more hard to merge anyway. And I guess soon a binary > >>>> release could be done. > >>>> > >>>> Jacques > >>>> > >>>> ----- Message d'origine ----- De : "David E Jones" > >>>> <[hidden email]> > >>>> À : <[hidden email]> > >>>> Cc : <[hidden email]> > >>>> Envoyé : jeudi 27 septembre 2007 17:30 > >>>> Objet : Re: svn commit: r578422 - > >>>> /ofbiz/branches/release4.0/framework/service/servicedef/services.xml > >>>> > >>>> > >>>>> This change probably won't have any effect in the branch as the > >>>>> service semaphore stuff was only added a couple of weeks ago, > >> long > >>>> after the branch was done, and it's a new feature in the framework > >>>> that shouldn't go into the branch. > >>>>> Using it in the branch shouldn't cause things to not function, but > >>>>> there will be a XML validation error every time the file is > >>>> read. > >>>>> -David > >>>>> > >>>>> > >>>>> [hidden email] wrote: > >>>>>> Author: jleroux > >>>>>> Date: Sat Sep 22 05:50:10 2007 > >>>>>> New Revision: 578422 > >>>>>> > >>>>>> URL: http://svn.apache.org/viewvc?rev=578422&view=rev > >>>>>> Log: > >>>>>> Applied fix from trunk for revision: 577097 > >>>>>> > >>>>>> Modified: > >>>>>> > >>>>>> ofbiz/branches/release4.0/framework/service/servicedef/services.xml > >>>>>> > >>>>>> Modified: > >>>>>> ofbiz/branches/release4.0/framework/service/servicedef/services.xml > >>>>>> URL: > >> > >> > >>>>>> ============================================================================== > >>>>>> > >>>>>> --- > >>>>>> ofbiz/branches/release4.0/framework/service/servicedef/services.xml > >>>>>> (original) > >>>>>> +++ > >>>>>> ofbiz/branches/release4.0/framework/service/servicedef/services.xml > >>>>>> Sat Sep 22 05:50:10 2007 > >>>>>> @@ -26,7 +26,7 @@ > >>>>>> > >>>>>> <!-- Service Engine Services --> > >>>>>> <service name="purgeOldJobs" engine="java" > >>>>>> - location="org.ofbiz.service.ServiceUtil" > >>>>>> invoke="purgeOldJobs" auth="true" use-transaction="false"> > >>>>>> + location="org.ofbiz.service.ServiceUtil" > >>>>>> invoke="purgeOldJobs" auth="true" use-transaction="false" > >>>> semaphore="wait"> > >>>>>> <description>Cleans out old jobs which have been around longer > >>>>>> then what is defined in serviceengine.xml</description> > >>>>>> <required-permissions join-type="AND"> > >>>>>> <check-permission permission="SERVICE_INVOKE_ANY"/> > >>>>>> > >>>>>> > >>>> > >> > > > > > |
«
Return to OFBiz - Dev
|
1 view|%1 views
| Free forum by Nabble | Edit this page |