Making the dev process work for me.

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Making the dev process work for me.

chris snow-2
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 hard work!  Another 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 prop
Reply | Threaded
Open this post in threaded view
|

Re: Making the dev process work for me.

chris snow-2
On 15 May 2010 07:38, "chris snow" <[hidden email]> 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
Reply | Threaded
Open this post in threaded view
|

Re: Making the dev process work for me.

Ean Schuessler
If you could make your changes in a cloned GIT repository we might be
able to review and commit them en masse.

On 05/15/2010 01:45 AM, chris snow wrote:

> On 15 May 2010 07:38, "chris snow"<[hidden email]>  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?
Reply | Threaded
Open this post in threaded view
|

Re: Making the dev process work for me.

Chris Snow-3
Thanks Ean - I will take a look at GIT...

> If you could make your changes in a cloned GIT repository we might be
> able to review and commit them en masse.
>
> On 05/15/2010 01:45 AM, chris snow wrote:
>> On 15 May 2010 07:38, "chris snow"<[hidden email]>  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?
>


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

Tel: 01453 890660
Mob: 07944 880950
Www: www.snowconsulting.co.uk

Reply | Threaded
Open this post in threaded view
|

Re: Making the dev process work for me.

Erwan de FERRIERES
In reply to this post by chris snow-2
Le 15/05/2010 08:38, chris snow a écrit :

> 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 hard work!  Another 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 prop
>
Hi Chris,

sorry for taking so long for committing your patch... I was a bit busy,
and this has been out of my head... Moreover, I was like Jacques
sometimes ago with some Internet problems !

So, thanks for those who reviewed and committed instead of me !

--
Erwan de FERRIERES
www.nereide.biz
Reply | Threaded
Open this post in threaded view
|

Re: Making the dev process work for me.

Chris Snow-3
Hi Erwan,

The problem with commit lag is not caused by any one person, it is a
problem with the process.  Based on feedback from others, I think the way
around it will be to get my own svn/git branch running and do my work
there.  I can then submit patches back upstream and not have to worry
about the commit lag.

Many thanks,

Chris


> Hi Chris,
>
> sorry for taking so long for committing your patch... I was a bit busy,
> and this has been out of my head... Moreover, I was like Jacques
> sometimes ago with some Internet problems !
>
> So, thanks for those who reviewed and committed instead of me !
>
> --
> Erwan de FERRIERES
> www.nereide.biz
>