Agreed. Since I'm not a committer, any volunteers to commit my WODEN-14 patch to trunk please ?:)
Kind Regards,
Graham.
_____________________________________________
Graham C Turrell CEng, MBCS
Chartered IT Practitioner
WebSphere ESB Foundation Technologies
DE3F16 / MP 211
IBM Labs
Hursley Park
Winchester, Hampshire
England. SO21 2JN
Tel +44-(0)1962-815018
email: [EMAIL PROTECTED]
"No army can withstand the force of an idea whose time
has come.". -Victor Hugo
Eran Chinthaka
<[EMAIL PROTECTED]
urce.lk> To
[email protected]
09/09/2006 11:38 cc
Subject
Please respond to Re: WODEN-14 patch attached to JIRA
[EMAIL PROTECTED]
he.org
A definite +1 for Jeremy's thoughts.
I also was looking at the branches and was thinking why its happening
like this. In Apache its 99.9% of the time we have Commit-then-review
policy.
-- Chinthaka
Jeremy Hughes wrote:
> We seem to be creating branches for lots of JIRAs nowadays.
>
> I know I set an example by creating WODEN-40 but that was because I
> wanted to create a "mini-revolution" - there were a lot of API changes
> I needed to make and I didn't want to disrupt development on trunk.
> Also, I thought it would take a not-insignificant amount of time to
> code the changes (unfortunately a self-fulfilling prophecy there), so
> I felt that rather than coding them privately over a long period, I
> would check them in to a branch for all to see and potentially
> contribute to. There are overheads to using branches: merging the
> changes to the trunk into the branch periodically, merging the code
> into trunk is a review-then-commit process (rather than the normal
> commit-then-review) so a vote is required to merge the branch into
> trunk, then of course there's the actual deed of merging the branch
> into the trunk. On the other hand, these overheads can be quite small
> for small short lived (mini-revoluation) branches.
>
> What you've got here in WODEN-14 is evolutionary (IMO) and not
> revolutionary so can simply go straight into the trunk. I appreciate
> we're gearing up for a milestone release, but the timing of that has
> been put into question now. If the patch is good (could you provide
> some testscases?) then I'd like to check it into the trunk. If we hold
> out WODEN-14 until after the milestone release, we should do just that
> - ie leave the patch on the JIRA rather than creating a branch.
>
> Cheers,
> Jeremy
>
> On 9/8/06, Graham Turrell <[EMAIL PROTECTED]> wrote:
>>
>> Hi John,
>>
>> I have attached a patch file to the WODEN-14 jira covering a working
>> framework and SimpleURIResolver - hopefully enough from
>> which to create a subversion branch. Could you please create the
>> branch, or
>> let me know if you need anything more in order to do that?
>>
>> Cheers.
>>
>> Kind Regards,
>>
>> Graham.
>> _____________________________________________
>> Graham C Turrell CEng, MBCS
>> Chartered IT Practitioner
>>
>> WebSphere ESB Foundation Technologies
>> DE3F16 / MP 211
>> IBM Labs
>> Hursley Park
>> Winchester, Hampshire
>> England. SO21 2JN
>>
>> Tel +44-(0)1962-815018
>> email: [EMAIL PROTECTED]
>>
>> "No army can withstand the force of an idea whose time
>> has come.". -Victor Hugo
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
(See attached file: signature.asc)
signature.asc
Description: Binary data
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
