You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by Paul Fremantle <pz...@gmail.com> on 2005/12/22 15:03:19 UTC
New function
Folks
Can I suggest the following model for commits?
For fixes to the existing codebase, please document the svn checkins well (I
know I am not always the best... I will improve my comments).
For new mediators, new function or refactoring, please we please check into
scratch and then when it is "good" please post a note to the list asking
people to review before committing to head.
Paul
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
Re: New function
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
+1 ... and in some sense *because* Synapse is at an early stage HEAD
instability is to be expected.
Sanjiva.
On Sat, 2005-12-24 at 13:50 -0500, Davanum Srinivas wrote:
> Paul,
>
> - Refactorings will be a big pain in the neck.
> - Stability can be ensured by test cases.
> - Optimizing imports, Reformatting code using a common tool can help
> with common coding style.
> - I've seen code go bad real quickly and out of date if it is not in
> the HEAD. (example there was a JAXB extension in scratch are of Axis2
> that was written for JAXB RI, now it's completely unusable, same with
> a JAXWS stuff). People just give up after a while.
>
> thanks,
> dims
>
> On 12/24/05, Paul Fremantle <pz...@gmail.com> wrote:
> > Dims
> >
> > I had two reasons.
> >
> > 1) I think it will help with frequent releases, because the HEAD code should
> > only add new function when it is stable.
> >
> > 2) We are still at an early stage. I think there are potentially large
> > changes we could do, and major new function. We still have not yet got a
> > common coding style, and I think this model could encourage us all to review
> > each others work before posting it to HEAD.
> >
> > However, I am not wedded to this idea. If people don't like it, please say.
> >
> > Paul
> >
> >
> >
> >
> > On 12/22/05, Davanum Srinivas < davanum@gmail.com> wrote:
> > >
> > > Paul,
> > >
> > > why, if i may ask?
> > >
> > > -- dims
> > >
> > > On 12/22/05, Paul Fremantle <pz...@gmail.com> wrote:
> > > > Folks
> > > >
> > > > Can I suggest the following model for commits?
> > > >
> > > > For fixes to the existing codebase, please document the svn checkins
> > well (I
> > > > know I am not always the best... I will improve my comments).
> > > >
> > > > For new mediators, new function or refactoring, please we please check
> > into
> > > > scratch and then when it is "good" please post a note to the list asking
> > > > people to review before committing to head.
> > > >
> > > >
> > > > Paul
> > > >
> > > > --
> > > > Paul Fremantle
> > > > VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
> > > >
> > > > http://bloglines.com/blog/paulfremantle
> > > > paul@wso2.com
> > > >
> > > > "Oxygenating the Web Service Platform", www.wso2.com
> > > >
> > >
> > >
> > > --
> > > Davanum Srinivas : http://wso2.com/blogs/
> > >
> > >
> > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail:
> > synapse-dev-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: synapse-dev-help@ws.apache.org
> > >
> > >
> >
> >
> >
> > --
> >
> > Paul Fremantle
> > VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
> >
> > http://bloglines.com/blog/paulfremantle
> > paul@wso2.com
> >
> > "Oxygenating the Web Service Platform", www.wso2.com
> >
>
>
> --
> Davanum Srinivas : http://wso2.com/blogs/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: synapse-dev-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org
Re: New function
Posted by Davanum Srinivas <da...@gmail.com>.
Paul,
- Refactorings will be a big pain in the neck.
- Stability can be ensured by test cases.
- Optimizing imports, Reformatting code using a common tool can help
with common coding style.
- I've seen code go bad real quickly and out of date if it is not in
the HEAD. (example there was a JAXB extension in scratch are of Axis2
that was written for JAXB RI, now it's completely unusable, same with
a JAXWS stuff). People just give up after a while.
thanks,
dims
On 12/24/05, Paul Fremantle <pz...@gmail.com> wrote:
> Dims
>
> I had two reasons.
>
> 1) I think it will help with frequent releases, because the HEAD code should
> only add new function when it is stable.
>
> 2) We are still at an early stage. I think there are potentially large
> changes we could do, and major new function. We still have not yet got a
> common coding style, and I think this model could encourage us all to review
> each others work before posting it to HEAD.
>
> However, I am not wedded to this idea. If people don't like it, please say.
>
> Paul
>
>
>
>
> On 12/22/05, Davanum Srinivas < davanum@gmail.com> wrote:
> >
> > Paul,
> >
> > why, if i may ask?
> >
> > -- dims
> >
> > On 12/22/05, Paul Fremantle <pz...@gmail.com> wrote:
> > > Folks
> > >
> > > Can I suggest the following model for commits?
> > >
> > > For fixes to the existing codebase, please document the svn checkins
> well (I
> > > know I am not always the best... I will improve my comments).
> > >
> > > For new mediators, new function or refactoring, please we please check
> into
> > > scratch and then when it is "good" please post a note to the list asking
> > > people to review before committing to head.
> > >
> > >
> > > Paul
> > >
> > > --
> > > Paul Fremantle
> > > VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
> > >
> > > http://bloglines.com/blog/paulfremantle
> > > paul@wso2.com
> > >
> > > "Oxygenating the Web Service Platform", www.wso2.com
> > >
> >
> >
> > --
> > Davanum Srinivas : http://wso2.com/blogs/
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> synapse-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: synapse-dev-help@ws.apache.org
> >
> >
>
>
>
> --
>
> Paul Fremantle
> VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
>
> http://bloglines.com/blog/paulfremantle
> paul@wso2.com
>
> "Oxygenating the Web Service Platform", www.wso2.com
>
--
Davanum Srinivas : http://wso2.com/blogs/
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org
Re: New function
Posted by Paul Fremantle <pz...@gmail.com>.
Dims
I had two reasons.
1) I think it will help with frequent releases, because the HEAD code should
only add new function when it is stable.
2) We are still at an early stage. I think there are potentially large
changes we could do, and major new function. We still have not yet got a
common coding style, and I think this model could encourage us all to review
each others work before posting it to HEAD.
However, I am not wedded to this idea. If people don't like it, please say.
Paul
On 12/22/05, Davanum Srinivas <da...@gmail.com> wrote:
>
> Paul,
>
> why, if i may ask?
>
> -- dims
>
> On 12/22/05, Paul Fremantle <pz...@gmail.com> wrote:
> > Folks
> >
> > Can I suggest the following model for commits?
> >
> > For fixes to the existing codebase, please document the svn checkins
> well (I
> > know I am not always the best... I will improve my comments).
> >
> > For new mediators, new function or refactoring, please we please check
> into
> > scratch and then when it is "good" please post a note to the list asking
> > people to review before committing to head.
> >
> >
> > Paul
> >
> > --
> > Paul Fremantle
> > VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
> >
> > http://bloglines.com/blog/paulfremantle
> > paul@wso2.com
> >
> > "Oxygenating the Web Service Platform", www.wso2.com
> >
>
>
> --
> Davanum Srinivas : http://wso2.com/blogs/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: synapse-dev-help@ws.apache.org
>
>
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
Re: New function
Posted by Davanum Srinivas <da...@gmail.com>.
Paul,
why, if i may ask?
-- dims
On 12/22/05, Paul Fremantle <pz...@gmail.com> wrote:
> Folks
>
> Can I suggest the following model for commits?
>
> For fixes to the existing codebase, please document the svn checkins well (I
> know I am not always the best... I will improve my comments).
>
> For new mediators, new function or refactoring, please we please check into
> scratch and then when it is "good" please post a note to the list asking
> people to review before committing to head.
>
>
> Paul
>
> --
> Paul Fremantle
> VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
>
> http://bloglines.com/blog/paulfremantle
> paul@wso2.com
>
> "Oxygenating the Web Service Platform", www.wso2.com
>
--
Davanum Srinivas : http://wso2.com/blogs/
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org