Making the dev process work...

[Chris Snow-3]

A while back, I had a small improvement committed to provide field tooltip
help.

I now have the time consuming process of extracting the tooltip help text
from the manager references and putting it into the xml property files.

The problem is that I have to rely on commiters to take my patches, review
and commit them.  Erwan is kindly reviewing my patch for the ProductStore
and will hopefully commit it at some stage.  However, committers have
other priorities and getting the huge amount of patches that I will be
providing to be committed is going to be very timeconsuming!  Contributing
to the problem is that I don't want to spend more that half a day on a
single patch - I can't aford to lose time on writing patches that may not
get committed.

Is it possible to give fine grained svn access, I.e. just to the property
files that contain the field descriptions?

Any other ideas?

Many thanks,


Chris

[Scott Gray-2]

No it's not possible (well technically it is but it's very unlikely to happen).

Just be patient and they'll get committed.

Regards
Scott

HotWax Media
http://www.hotwaxmedia.com

On 15/05/2010, at 6:56 PM, Chris Snow wrote:

> A while back, I had a small improvement committed to provide field tooltip
> help.
>
> I now have the time consuming process of extracting the tooltip help text
> from the manager references and putting it into the xml property files.
>
> The problem is that I have to rely on commiters to take my patches, review
> and commit them.  Erwan is kindly reviewing my patch for the ProductStore
> and will hopefully commit it at some stage.  However, committers have
> other priorities and getting the huge amount of patches that I will be
> providing to be committed is going to be very timeconsuming!  Contributing
> to the problem is that I don't want to spend more that half a day on a
> single patch - I can't aford to lose time on writing patches that may not
> get committed.
>
> Is it possible to give fine grained svn access, I.e. just to the property
> files that contain the field descriptions?
>
> Any other ideas?
>
> Many thanks,
>
>
> Chris
>

[Adrian Crum-2]

Yeah, be patient. I had patches sitting in Jira for years before they were committed.

-Adrian


--- On Sat, 5/15/10, Scott Gray <[hidden email]> wrote:

> From: Scott Gray <[hidden email]>
> Subject: Re: Making the dev process work...
> To: [hidden email]
> Date: Saturday, May 15, 2010, 1:42 AM
> No it's not possible (well
> technically it is but it's very unlikely to happen).
>
> Just be patient and they'll get committed.
>
> Regards
> Scott
>
> HotWax Media
> http://www.hotwaxmedia.com
>
> On 15/05/2010, at 6:56 PM, Chris Snow wrote:
>
> > A while back, I had a small improvement committed to
> provide field tooltip
> > help.
> >
> > I now have the time consuming process of extracting
> the tooltip help text
> > from the manager references and putting it into the
> xml property files.
> >
> > The problem is that I have to rely on commiters to
> take my patches, review
> > and commit them.  Erwan is kindly reviewing my
> patch for the ProductStore
> > and will hopefully commit it at some stage. 
> However, committers have
> > other priorities and getting the huge amount of
> patches that I will be
> > providing to be committed is going to be very
> timeconsuming!  Contributing
> > to the problem is that I don't want to spend more that
> half a day on a
> > single patch - I can't aford to lose time on writing
> patches that may not
> > get committed.
> >
> > Is it possible to give fine grained svn access, I.e.
> just to the property
> > files that contain the field descriptions?
> >
> > Any other ideas?
> >
> > Many thanks,
> >
> >
> > Chris
> >
>
>

[Chris Snow-3]

If there is one patch per entity, only one or two patches waiting to be
committed at any one time, one month to commit each patch, that's alot of
patience (100+ months)!

It sounds like my options are:

A) not bother doing anything
B) setup my own local svn that is a mirror of the apache svn server

> Yeah, be patient. I had patches sitting in Jira for years before they were
> committed.
>
> -Adrian
>
>
> --- On Sat, 5/15/10, Scott Gray <[hidden email]> wrote:
>
>> From: Scott Gray <[hidden email]>
>> Subject: Re: Making the dev process work...
>> To: [hidden email]
>> Date: Saturday, May 15, 2010, 1:42 AM
>> No it's not possible (well
>> technically it is but it's very unlikely to happen).
>>
>> Just be patient and they'll get committed.
>>
>> Regards
>> Scott
>>
>> HotWax Media
>> http://www.hotwaxmedia.com
>>
>> On 15/05/2010, at 6:56 PM, Chris Snow wrote:
>>
>> > A while back, I had a small improvement committed to
>> provide field tooltip
>> > help.
>> >
>> > I now have the time consuming process of extracting
>> the tooltip help text
>> > from the manager references and putting it into the
>> xml property files.
>> >
>> > The problem is that I have to rely on commiters to
>> take my patches, review
>> > and commit them.  Erwan is kindly reviewing my
>> patch for the ProductStore
>> > and will hopefully commit it at some stage. 
>> However, committers have
>> > other priorities and getting the huge amount of
>> patches that I will be
>> > providing to be committed is going to be very
>> timeconsuming!  Contributing
>> > to the problem is that I don't want to spend more that
>> half a day on a
>> > single patch - I can't aford to lose time on writing
>> patches that may not
>> > get committed.
>> >
>> > Is it possible to give fine grained svn access, I.e.
>> just to the property
>> > files that contain the field descriptions?
>> >
>> > Any other ideas?
>> >
>> > Many thanks,
>> >
>> >
>> > Chris
>> >
>>
>>
>
>
>
>

--
Chris Snow - CEng MBCS CITP MBA (Tech Mgmt) (Open) CISSP

Tel: [phone]
Mob: [phone]
Www: www.snowconsulting.co.uk

[Marc Morin]

For non committers, like ourselves.  You must create your own svn repository, with a vendor branch to the ofbiz repository.

Then create your own branch of the raw trunk, to do your own local changes.  Package up these changes into patches, and post them back to the ofbiz project.... they may or may not be accepted.

But at least you can use your "private" modified version of ofbiz and it won't hold you up.

Marc Morin
Emforium Group Inc.
ALL-IN Software
519-772-6824 ext 201
[hidden email]

----- "Chris Snow" <[hidden email]> wrote:

> If there is one patch per entity, only one or two patches waiting to
> be
> committed at any one time, one month to commit each patch, that's alot
> of
> patience (100+ months)!
>
> It sounds like my options are:
>
> A) not bother doing anything
> B) setup my own local svn that is a mirror of the apache svn server
>
> > Yeah, be patient. I had patches sitting in Jira for years before
> they were
> > committed.
> >
> > -Adrian
> >
> >
> > --- On Sat, 5/15/10, Scott Gray <[hidden email]> wrote:
> >
> >> From: Scott Gray <[hidden email]>
> >> Subject: Re: Making the dev process work...
> >> To: [hidden email]
> >> Date: Saturday, May 15, 2010, 1:42 AM
> >> No it's not possible (well
> >> technically it is but it's very unlikely to happen).
> >>
> >> Just be patient and they'll get committed.
> >>
> >> Regards
> >> Scott
> >>
> >> HotWax Media
> >> http://www.hotwaxmedia.com
> >>
> >> On 15/05/2010, at 6:56 PM, Chris Snow wrote:
> >>
> >> > A while back, I had a small improvement committed to
> >> provide field tooltip
> >> > help.
> >> >
> >> > I now have the time consuming process of extracting
> >> the tooltip help text
> >> > from the manager references and putting it into the
> >> xml property files.
> >> >
> >> > The problem is that I have to rely on commiters to
> >> take my patches, review
> >> > and commit them.  Erwan is kindly reviewing my
> >> patch for the ProductStore
> >> > and will hopefully commit it at some stage. 
> >> However, committers have
> >> > other priorities and getting the huge amount of
> >> patches that I will be
> >> > providing to be committed is going to be very
> >> timeconsuming!  Contributing
> >> > to the problem is that I don't want to spend more that
> >> half a day on a
> >> > single patch - I can't aford to lose time on writing
> >> patches that may not
> >> > get committed.
> >> >
> >> > Is it possible to give fine grained svn access, I.e.
> >> just to the property
> >> > files that contain the field descriptions?
> >> >
> >> > Any other ideas?
> >> >
> >> > Many thanks,
> >> >
> >> >
> >> > Chris
> >> >
> >>
> >>
> >
> >
> >
> >
>
>
> --
> Chris Snow - CEng MBCS CITP MBA (Tech Mgmt) (Open) CISSP
>
> Tel: [phone]
> Mob: [phone]
> Www: www.snowconsulting.co.uk

[chris snow-2]

Thanks for the tip Marc.  If I have my own svn repository, there doesn't
seem to be any value to me in providing upstream patches that may not get
committed?

On 15 May 2010 12:16, "Marc Morin" <[hidden email]> wrote:

For non committers, like ourselves.  You must create your own svn
repository, with a vendor branch to the ofbiz repository.

Then create your own branch of the raw trunk, to do your own local changes.
 Package up these changes into patches, and post them back to the ofbiz
project.... they may or may not be accepted.

But at least you can use your "private" modified version of ofbiz and it
won't hold you up.

Marc Morin
Emforium Group Inc.
ALL-IN Software
519-772-6824 ext 201
[hidden email]


----- "Chris Snow" <[hidden email]> wrote:

> If there is one patch per entity, only o...

[Marc Morin]

As ofbiz developers, we should all be aligned in providing upstream patches that fix bugs, etc.. to the ofbiz project.

It's in your interest to minimize the differences between your copy of ofbiz and the "official" one. You'll need to be clear about what is "specific" to your application vs core changes.  Core changes should be submitted.

This strategy just makes it easier for you to deal with the "patch latency" inherent in the ofbiz review-then-commit practise for non-committers.

Marc Morin
Emforium Group Inc.
ALL-IN Software
519-772-6824 ext 201
[hidden email]

----- "chris snow" <[hidden email]> wrote:

> Thanks for the tip Marc.  If I have my own svn repository, there
> doesn't
> seem to be any value to me in providing upstream patches that may not
> get
> committed?
>
> On 15 May 2010 12:16, "Marc Morin" <[hidden email]> wrote:
>
> For non committers, like ourselves.  You must create your own svn
> repository, with a vendor branch to the ofbiz repository.
>
> Then create your own branch of the raw trunk, to do your own local
> changes.
>  Package up these changes into patches, and post them back to the
> ofbiz
> project.... they may or may not be accepted.
>
> But at least you can use your "private" modified version of ofbiz and
> it
> won't hold you up.
>
> Marc Morin
> Emforium Group Inc.
> ALL-IN Software
> 519-772-6824 ext 201
> [hidden email]
>
>
> ----- "Chris Snow" <[hidden email]> wrote:
>
> > If there is one patch per entity, only o...

[chris snow-2]

Makes sense - thanks Marc.

On 15 May 2010 12:29, "Marc Morin" <[hidden email]> wrote:

As ofbiz developers, we should all be aligned in providing upstream patches
that fix bugs, etc.. to the ofbiz project.

It's in your interest to minimize the differences between your copy of ofbiz
and the "official" one. You'll need to be clear about what is "specific" to
your application vs core changes.  Core changes should be submitted.

This strategy just makes it easier for you to deal with the "patch latency"
inherent in the ofbiz review-then-commit practise for non-committers.


Marc Morin
Emforium Group Inc.
ALL-IN Software
519-772-6824 ext 201
[hidden email]

----- "chris snow" <[hidden email]> wrote:

> Thanks for the tip Marc. If I have my own s...

[Adrian Crum-2]

Sometimes volunteer effort comes in spurts. There is a good chance you'll have a dozen patches sitting there for a while, and then they all get committted in one weekend.

If you give up and not upload patches, then when that volunteer time becomes available there will be nothing to commit.

-Adrian

--- On Sat, 5/15/10, Chris Snow <[hidden email]> wrote:

> From: Chris Snow <[hidden email]>
> Subject: Re: Making the dev process work...
> To: [hidden email]
> Date: Saturday, May 15, 2010, 2:30 AM
> If there is one patch per entity,
> only one or two patches waiting to be
> committed at any one time, one month to commit each patch,
> that's alot of
> patience (100+ months)!
>
> It sounds like my options are:
>
> A) not bother doing anything
> B) setup my own local svn that is a mirror of the apache
> svn server
>
> > Yeah, be patient. I had patches sitting in Jira for
> years before they were
> > committed.
> >
> > -Adrian
> >
> >
> > --- On Sat, 5/15/10, Scott Gray <[hidden email]>
> wrote:
> >
> >> From: Scott Gray <[hidden email]>
> >> Subject: Re: Making the dev process work...
> >> To: [hidden email]
> >> Date: Saturday, May 15, 2010, 1:42 AM
> >> No it's not possible (well
> >> technically it is but it's very unlikely to
> happen).
> >>
> >> Just be patient and they'll get committed.
> >>
> >> Regards
> >> Scott
> >>
> >> HotWax Media
> >> http://www.hotwaxmedia.com
> >>
> >> On 15/05/2010, at 6:56 PM, Chris Snow wrote:
> >>
> >> > A while back, I had a small improvement
> committed to
> >> provide field tooltip
> >> > help.
> >> >
> >> > I now have the time consuming process of
> extracting
> >> the tooltip help text
> >> > from the manager references and putting it
> into the
> >> xml property files.
> >> >
> >> > The problem is that I have to rely on
> commiters to
> >> take my patches, review
> >> > and commit them.  Erwan is kindly reviewing
> my
> >> patch for the ProductStore
> >> > and will hopefully commit it at some
> stage. 
> >> However, committers have
> >> > other priorities and getting the huge amount
> of
> >> patches that I will be
> >> > providing to be committed is going to be
> very
> >> timeconsuming!  Contributing
> >> > to the problem is that I don't want to spend
> more that
> >> half a day on a
> >> > single patch - I can't aford to lose time on
> writing
> >> patches that may not
> >> > get committed.
> >> >
> >> > Is it possible to give fine grained svn
> access, I.e.
> >> just to the property
> >> > files that contain the field descriptions?
> >> >
> >> > Any other ideas?
> >> >
> >> > Many thanks,
> >> >
> >> >
> >> > Chris
> >> >
> >>
> >>
> >
> >
> >
> >
>
>
> --
> Chris Snow - CEng MBCS CITP MBA (Tech Mgmt) (Open) CISSP
>
> Tel: [phone]
> Mob: [phone]
> Www: www.snowconsulting.co.uk
>
>

[Jacques Le Roux]

Chris,

I'm almost finished with the layered lookups effort. I will then have a look at your work, if Erwan does not beat me on it. If I
recall well, we were reluctant to commit as it was only a temporary workaround, isn'it?

Jacques

from: "Adrian Crum" <[hidden email]>

> Sometimes volunteer effort comes in spurts. There is a good chance you'll have a dozen patches sitting there for a while, and then
> they all get committted in one weekend.
>
> If you give up and not upload patches, then when that volunteer time becomes available there will be nothing to commit.
>
> -Adrian
>
> --- On Sat, 5/15/10, Chris Snow <[hidden email]> wrote:
>
>> From: Chris Snow <[hidden email]>
>> Subject: Re: Making the dev process work...
>> To: [hidden email]
>> Date: Saturday, May 15, 2010, 2:30 AM
>> If there is one patch per entity,
>> only one or two patches waiting to be
>> committed at any one time, one month to commit each patch,
>> that's alot of
>> patience (100+ months)!
>>
>> It sounds like my options are:
>>
>> A) not bother doing anything
>> B) setup my own local svn that is a mirror of the apache
>> svn server
>>
>> > Yeah, be patient. I had patches sitting in Jira for
>> years before they were
>> > committed.
>> >
>> > -Adrian
>> >
>> >
>> > --- On Sat, 5/15/10, Scott Gray <[hidden email]>
>> wrote:
>> >
>> >> From: Scott Gray <[hidden email]>
>> >> Subject: Re: Making the dev process work...
>> >> To: [hidden email]
>> >> Date: Saturday, May 15, 2010, 1:42 AM
>> >> No it's not possible (well
>> >> technically it is but it's very unlikely to
>> happen).
>> >>
>> >> Just be patient and they'll get committed.
>> >>
>> >> Regards
>> >> Scott
>> >>
>> >> HotWax Media
>> >> http://www.hotwaxmedia.com
>> >>
>> >> On 15/05/2010, at 6:56 PM, Chris Snow wrote:
>> >>
>> >> > A while back, I had a small improvement
>> committed to
>> >> provide field tooltip
>> >> > help.
>> >> >
>> >> > I now have the time consuming process of
>> extracting
>> >> the tooltip help text
>> >> > from the manager references and putting it
>> into the
>> >> xml property files.
>> >> >
>> >> > The problem is that I have to rely on
>> commiters to
>> >> take my patches, review
>> >> > and commit them. Erwan is kindly reviewing
>> my
>> >> patch for the ProductStore
>> >> > and will hopefully commit it at some
>> stage.
>> >> However, committers have
>> >> > other priorities and getting the huge amount
>> of
>> >> patches that I will be
>> >> > providing to be committed is going to be
>> very
>> >> timeconsuming! Contributing
>> >> > to the problem is that I don't want to spend
>> more that
>> >> half a day on a
>> >> > single patch - I can't aford to lose time on
>> writing
>> >> patches that may not
>> >> > get committed.
>> >> >
>> >> > Is it possible to give fine grained svn
>> access, I.e.
>> >> just to the property
>> >> > files that contain the field descriptions?
>> >> >
>> >> > Any other ideas?
>> >> >
>> >> > Many thanks,
>> >> >
>> >> >
>> >> > Chris
>> >> >
>> >>
>> >>
>> >
>> >
>> >
>> >
>>
>>
>> --
>> Chris Snow - CEng MBCS CITP MBA (Tech Mgmt) (Open) CISSP
>>
>> Tel: [phone]
>> Mob: [phone]
>> Www: www.snowconsulting.co.uk
>>
>>
>
>
>
>

[Bruno Busco]

I am doing it right now.
Please hold on.

-Bruno

2010/5/15 Jacques Le Roux <[hidden email]>

> Chris,
>
> I'm almost finished with the layered lookups effort. I will then have a
> look at your work, if Erwan does not beat me on it. If I recall well, we
> were reluctant to commit as it was only a temporary workaround, isn'it?
>
> Jacques
>
> from: "Adrian Crum" <[hidden email]>
>
>  Sometimes volunteer effort comes in spurts. There is a good chance you'll
>> have a dozen patches sitting there for a while, and then they all get
>> committted in one weekend.
>>
>> If you give up and not upload patches, then when that volunteer time
>> becomes available there will be nothing to commit.
>>
>> -Adrian
>>
>> --- On Sat, 5/15/10, Chris Snow <[hidden email]> wrote:
>>
>>  From: Chris Snow <[hidden email]>
>>> Subject: Re: Making the dev process work...
>>> To: [hidden email]
>>> Date: Saturday, May 15, 2010, 2:30 AM
>>> If there is one patch per entity,
>>> only one or two patches waiting to be
>>> committed at any one time, one month to commit each patch,
>>> that's alot of
>>> patience (100+ months)!
>>>
>>> It sounds like my options are:
>>>
>>> A) not bother doing anything
>>> B) setup my own local svn that is a mirror of the apache
>>> svn server
>>>
>>> > Yeah, be patient. I had patches sitting in Jira for
>>> years before they were
>>> > committed.
>>> >
>>> > -Adrian
>>> >
>>> >
>>> > --- On Sat, 5/15/10, Scott Gray <[hidden email]>
>>> wrote:
>>> >
>>> >> From: Scott Gray <[hidden email]>
>>> >> Subject: Re: Making the dev process work...
>>> >> To: [hidden email]
>>> >> Date: Saturday, May 15, 2010, 1:42 AM
>>> >> No it's not possible (well
>>> >> technically it is but it's very unlikely to
>>> happen).
>>> >>
>>> >> Just be patient and they'll get committed.
>>> >>
>>> >> Regards
>>> >> Scott
>>> >>
>>> >> HotWax Media
>>> >> http://www.hotwaxmedia.com
>>> >>
>>> >> On 15/05/2010, at 6:56 PM, Chris Snow wrote:
>>> >>
>>> >> > A while back, I had a small improvement
>>> committed to
>>> >> provide field tooltip
>>> >> > help.
>>> >> >
>>> >> > I now have the time consuming process of
>>> extracting
>>> >> the tooltip help text
>>> >> > from the manager references and putting it
>>> into the
>>> >> xml property files.
>>> >> >
>>> >> > The problem is that I have to rely on
>>> commiters to
>>> >> take my patches, review
>>> >> > and commit them. Erwan is kindly reviewing
>>> my
>>> >> patch for the ProductStore
>>> >> > and will hopefully commit it at some
>>> stage.
>>> >> However, committers have
>>> >> > other priorities and getting the huge amount
>>> of
>>> >> patches that I will be
>>> >> > providing to be committed is going to be
>>> very
>>> >> timeconsuming! Contributing
>>> >> > to the problem is that I don't want to spend
>>> more that
>>> >> half a day on a
>>> >> > single patch - I can't aford to lose time on
>>> writing
>>> >> patches that may not
>>> >> > get committed.
>>> >> >
>>> >> > Is it possible to give fine grained svn
>>> access, I.e.
>>> >> just to the property
>>> >> > files that contain the field descriptions?
>>> >> >
>>> >> > Any other ideas?
>>> >> >
>>> >> > Many thanks,
>>> >> >
>>> >> >
>>> >> > Chris
>>> >> >
>>> >>
>>> >>
>>> >
>>> >
>>> >
>>> >
>>>
>>>
>>> --
>>> Chris Snow - CEng MBCS CITP MBA (Tech Mgmt) (Open) CISSP
>>>
>>> Tel: [phone]
>>> Mob: [phone]
>>> Www: www.snowconsulting.co.uk
>>>
>>>
>>>
>>
>>
>>
>>
>
>

[Chris Snow-3]

Hi Jacques,

The method for displaying the text may be improved, but the actual text
content will probably not need to change.

Many thanks,

Chris

On 15/05/10 17:06, Jacques Le Roux wrote:

> Chris,
>
> I'm almost finished with the layered lookups effort. I will then have
> a look at your work, if Erwan does not beat me on it. If I recall
> well, we were reluctant to commit as it was only a temporary
> workaround, isn'it?
>
> Jacques
>
> from: "Adrian Crum" <[hidden email]>
>> Sometimes volunteer effort comes in spurts. There is a good chance
>> you'll have a dozen patches sitting there for a while, and then they
>> all get committted in one weekend.
>>
>> If you give up and not upload patches, then when that volunteer time
>> becomes available there will be nothing to commit.
>>
>> -Adrian
>>
>> --- On Sat, 5/15/10, Chris Snow <[hidden email]> wrote:
>>
>>> From: Chris Snow <[hidden email]>
>>> Subject: Re: Making the dev process work...
>>> To: [hidden email]
>>> Date: Saturday, May 15, 2010, 2:30 AM
>>> If there is one patch per entity,
>>> only one or two patches waiting to be
>>> committed at any one time, one month to commit each patch,
>>> that's alot of
>>> patience (100+ months)!
>>>
>>> It sounds like my options are:
>>>
>>> A) not bother doing anything
>>> B) setup my own local svn that is a mirror of the apache
>>> svn server
>>>
>>> > Yeah, be patient. I had patches sitting in Jira for
>>> years before they were
>>> > committed.
>>> >
>>> > -Adrian
>>> >
>>> >
>>> > --- On Sat, 5/15/10, Scott Gray <[hidden email]>
>>> wrote:
>>> >
>>> >> From: Scott Gray <[hidden email]>
>>> >> Subject: Re: Making the dev process work...
>>> >> To: [hidden email]
>>> >> Date: Saturday, May 15, 2010, 1:42 AM
>>> >> No it's not possible (well
>>> >> technically it is but it's very unlikely to
>>> happen).
>>> >>
>>> >> Just be patient and they'll get committed.
>>> >>
>>> >> Regards
>>> >> Scott
>>> >>
>>> >> HotWax Media
>>> >> http://www.hotwaxmedia.com
>>> >>
>>> >> On 15/05/2010, at 6:56 PM, Chris Snow wrote:
>>> >>
>>> >> > A while back, I had a small improvement
>>> committed to
>>> >> provide field tooltip
>>> >> > help.
>>> >> >
>>> >> > I now have the time consuming process of
>>> extracting
>>> >> the tooltip help text
>>> >> > from the manager references and putting it
>>> into the
>>> >> xml property files.
>>> >> >
>>> >> > The problem is that I have to rely on
>>> commiters to
>>> >> take my patches, review
>>> >> > and commit them. Erwan is kindly reviewing
>>> my
>>> >> patch for the ProductStore
>>> >> > and will hopefully commit it at some
>>> stage.
>>> >> However, committers have
>>> >> > other priorities and getting the huge amount
>>> of
>>> >> patches that I will be
>>> >> > providing to be committed is going to be
>>> very
>>> >> timeconsuming! Contributing
>>> >> > to the problem is that I don't want to spend
>>> more that
>>> >> half a day on a
>>> >> > single patch - I can't aford to lose time on
>>> writing
>>> >> patches that may not
>>> >> > get committed.
>>> >> >
>>> >> > Is it possible to give fine grained svn
>>> access, I.e.
>>> >> just to the property
>>> >> > files that contain the field descriptions?
>>> >> >
>>> >> > Any other ideas?
>>> >> >
>>> >> > Many thanks,
>>> >> >
>>> >> >
>>> >> > Chris
>>> >> >
>>> >>
>>> >>
>>> >
>>> >
>>> >
>>> >
>>>
>>>
>>> --
>>> Chris Snow - CEng MBCS CITP MBA (Tech Mgmt) (Open) CISSP
>>>
>>> Tel: [phone]
>>> Mob: [phone]
>>> Www: www.snowconsulting.co.uk
>>>
>>>
>>
>>
>>
>>
>
>

[BJ Freeman]

I do B then put the patches in Jira in case someone wants to use them.

=========================
BJ Freeman
http://bjfreeman.elance.com
Strategic Power Office with Supplier Automation <http://www.businessesnetwork.com/automation/viewforum.php?f=93>
Specialtymarket.com <http://www.specialtymarket.com/>

Systems Integrator-- Glad to Assist

Chat  Y! messenger: bjfr33man
Linkedin
<http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro>


Chris Snow sent the following on 5/15/2010 2:30 AM:

> If there is one patch per entity, only one or two patches waiting to be
> committed at any one time, one month to commit each patch, that's alot of
> patience (100+ months)!
>
> It sounds like my options are:
>
> A) not bother doing anything
> B) setup my own local svn that is a mirror of the apache svn server
>
>> Yeah, be patient. I had patches sitting in Jira for years before they were
>> committed.
>>
>> -Adrian
>>
>>
>> --- On Sat, 5/15/10, Scott Gray <[hidden email]> wrote:
>>
>>> From: Scott Gray <[hidden email]>
>>> Subject: Re: Making the dev process work...
>>> To: [hidden email]
>>> Date: Saturday, May 15, 2010, 1:42 AM
>>> No it's not possible (well
>>> technically it is but it's very unlikely to happen).
>>>
>>> Just be patient and they'll get committed.
>>>
>>> Regards
>>> Scott
>>>
>>> HotWax Media
>>> http://www.hotwaxmedia.com
>>>
>>> On 15/05/2010, at 6:56 PM, Chris Snow wrote:
>>>
>>>> A while back, I had a small improvement committed to
>>> provide field tooltip
>>>> help.
>>>>
>>>> I now have the time consuming process of extracting
>>> the tooltip help text
>>>> from the manager references and putting it into the
>>> xml property files.
>>>> The problem is that I have to rely on commiters to
>>> take my patches, review
>>>> and commit them.  Erwan is kindly reviewing my
>>> patch for the ProductStore
>>>> and will hopefully commit it at some stage.
>>> However, committers have
>>>> other priorities and getting the huge amount of
>>> patches that I will be
>>>> providing to be committed is going to be very
>>> timeconsuming!  Contributing
>>>> to the problem is that I don't want to spend more that
>>> half a day on a
>>>> single patch - I can't aford to lose time on writing
>>> patches that may not
>>>> get committed.
>>>>
>>>> Is it possible to give fine grained svn access, I.e.
>>> just to the property
>>>> files that contain the field descriptions?
>>>>
>>>> Any other ideas?
>>>>
>>>> Many thanks,
>>>>
>>>>
>>>> Chris
>>>>
>>>
>>
>>
>>
>
>

[Bruno Busco]

OK Chris,
I reviewed and committed your patch in trunk at revision r944675.

Thank you for your work and patience.
-Bruno

2010/5/15 BJ Freeman <[hidden email]>

> I do B then put the patches in Jira in case someone wants to use them.
>
> =========================
> BJ Freeman
> http://bjfreeman.elance.com
> Strategic Power Office with Supplier Automation <
> http://www.businessesnetwork.com/automation/viewforum.php?f=93>
> Specialtymarket.com <http://www.specialtymarket.com/>
>
> Systems Integrator-- Glad to Assist
>
> Chat  Y! messenger: bjfr33man
> Linkedin
> <
> http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro
> >
>
>
> Chris Snow sent the following on 5/15/2010 2:30 AM:
> > If there is one patch per entity, only one or two patches waiting to be
> > committed at any one time, one month to commit each patch, that's alot of
> > patience (100+ months)!
> >
> > It sounds like my options are:
> >
> > A) not bother doing anything
> > B) setup my own local svn that is a mirror of the apache svn server
> >
> >> Yeah, be patient. I had patches sitting in Jira for years before they
> were
> >> committed.
> >>
> >> -Adrian
> >>
> >>
> >> --- On Sat, 5/15/10, Scott Gray <[hidden email]> wrote:
> >>
> >>> From: Scott Gray <[hidden email]>
> >>> Subject: Re: Making the dev process work...
> >>> To: [hidden email]
> >>> Date: Saturday, May 15, 2010, 1:42 AM
> >>> No it's not possible (well
> >>> technically it is but it's very unlikely to happen).
> >>>
> >>> Just be patient and they'll get committed.
> >>>
> >>> Regards
> >>> Scott
> >>>
> >>> HotWax Media
> >>> http://www.hotwaxmedia.com
> >>>
> >>> On 15/05/2010, at 6:56 PM, Chris Snow wrote:
> >>>
> >>>> A while back, I had a small improvement committed to
> >>> provide field tooltip
> >>>> help.
> >>>>
> >>>> I now have the time consuming process of extracting
> >>> the tooltip help text
> >>>> from the manager references and putting it into the
> >>> xml property files.
> >>>> The problem is that I have to rely on commiters to
> >>> take my patches, review
> >>>> and commit them.  Erwan is kindly reviewing my
> >>> patch for the ProductStore
> >>>> and will hopefully commit it at some stage.
> >>> However, committers have
> >>>> other priorities and getting the huge amount of
> >>> patches that I will be
> >>>> providing to be committed is going to be very
> >>> timeconsuming!  Contributing
> >>>> to the problem is that I don't want to spend more that
> >>> half a day on a
> >>>> single patch - I can't aford to lose time on writing
> >>> patches that may not
> >>>> get committed.
> >>>>
> >>>> Is it possible to give fine grained svn access, I.e.
> >>> just to the property
> >>>> files that contain the field descriptions?
> >>>>
> >>>> Any other ideas?
> >>>>
> >>>> Many thanks,
> >>>>
> >>>>
> >>>> Chris
> >>>>
> >>>
> >>
> >>
> >>
> >
> >
>
>
>

[Chris Snow-3]

Thanks Bruno!

On 15/05/10 17:38, Bruno Busco wrote:
> OK Chris,
> I reviewed and committed your patch in trunk at revision r944675.
>
> Thank you for your work and patience.
> -Bruno
>
>
>