You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lenya.apache.org by Rolf Kulemann <ro...@apache.org> on 2005/02/18 18:58:38 UTC
Re: svn commit: r154188 -
lenya/branches/BRANCH_1_2_X/src/webapp/lenya/usecase.xmap
On Thu, 2005-02-17 at 21:46, michi@apache.org wrote:
> Author: michi
> Date: Thu Feb 17 12:46:37 2005
> New Revision: 154188
>
> URL: http://svn.apache.org/viewcvs?view=rev&rev=154188
> Log:
> thanks to Linczak, Jonathan W. the root is not doubled anymore when creating a document
Should this patch also be applied for trunk?
Please keep the branches in sync.
--
Rolf Kulemann
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: svn commit: r154188 - lenya/branches/BRANCH_1_2_X/src/webapp/lenya/usecase.xmap
Posted by Michael Wechner <mi...@wyona.com>.
Gregor J. Rothfuss wrote:
> Michael Wechner wrote:
>
>> what about the time of the other person?
>
>
> i have ported dozens of fixes between the branches. it does not take
> much time with reasonable tool support.
this has nearly nothing todo with tool support. Why does stuff get
checked in which shouldn't? Because of the tools? I would rather say it
has got to do with testing.
> it definitely takes much less time than having two different persons
> look at the problem.
agreed
> also, what is it with "i have no time"?
hm?
> you'd think that everyone is in the same boat with regards to lack of
> time.
I am not the one telling other people within this project what they
should fix, except they break something or do a regression. I think we
should appreciate if somebody is improving stuff, no matter if it's
going to solve the full problem. Improvement is improvement.
How arrogant can one be not to appreciate the help of someone if
something is really getting improved? Why a community at all then?
Michi
--
Michael Wechner
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
michael.wechner@wyona.com michi@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: svn commit: r154188 - lenya/branches/BRANCH_1_2_X/src/webapp/lenya/usecase.xmap
Posted by "Gregor J. Rothfuss" <gr...@apache.org>.
Michael Wechner wrote:
> what about the time of the other person?
i have ported dozens of fixes between the branches. it does not take
much time with reasonable tool support. it definitely takes much less
time than having two different persons look at the problem. also, what
is it with "i have no time"? you'd think that everyone is in the same
boat with regards to lack of time.
--
Gregor J. Rothfuss
COO, Wyona Content Management Solutions http://wyona.com
Apache Lenya http://lenya.apache.org
gregor.rothfuss@wyona.com gregor@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: svn commit: r154188 - lenya/branches/BRANCH_1_2_X/src/webapp/lenya/usecase.xmap
Posted by Michael Wechner <mi...@wyona.com>.
Rolf Kulemann wrote:
>>nobody is saying that you or anyone else has to do this. Nobody is
>>forced to do further improvements. Improvements are voluntary!
>>
>>
>
>Of course, but we are talking about clean ups and unessacarry detective
>work here.
>
>
no, it's never just a cleanup ...
>>aren't bugfixes useful?!
>>
>>
>
>Of course in general. But we are core developers and should follow
>professional development rules and behavior.
>
is leaving bugs broken professional?
If somebody is cleaning up one side of the room on a voluntary basis
then also required to cleanup the other side? Where is the incentive to
start cleaning up at all?
> IMHO, we still have to
>learn to adopt this behavior.
>
>However, I would strongly recommend that we open bugzilla entries for
>patches applied for one branch and which should also be applied in
>another branch but have not yet.
>
I agreed to that long time ago (and also apologized for not doing so).
> This would save us all a lot of time;
>
>
what about the time of the other person?
Again, it's about fixing and not about messing up, such
that someone has to cleanup stuff. There is a huge difference I would say.
Michi
--
Michael Wechner
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
michael.wechner@wyona.com michi@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: svn
commit: r154188 - lenya/branches/BRANCH_1_2_X/src/webapp/lenya/usecase.xmap
Posted by Rolf Kulemann <ro...@apache.org>.
On Sat, 2005-02-19 at 15:32, Michael Wechner wrote:
> Rolf Kulemann wrote:
>
> >On Sat, 2005-02-19 at 14:16, Gregor J. Rothfuss wrote:
> >
> >
> >>Michael Wechner wrote:
> >>
> >>
> >>
> >>>it's easy to keep track of them. Since it's an improvement one will
> >>>notice anyway and hence it won't be forgotten if actually needed.
> >>>
> >>>
> >>it is not. i just found a *another* case this week where a patch had not
> >>been synced for months, in this case in the other direction.
> >>
> >>your "if actually needed" statement worries me. are you saying we should
> >>have to re-discover each bug for each branch?
> >>
> >>
> >
> >If I find myself wasting hours doing this rediscovering, I would be
> >really really annoyed.
> >
>
> nobody is saying that you or anyone else has to do this. Nobody is
> forced to do further improvements. Improvements are voluntary!
Of course, but we are talking about clean ups and unessacarry detective
work here.
>
> It definitely makes sense to use bugzilla for this
> and I apologize for not having done so far, but at the same time this
> also what the mailing list is good for, e.g.
> "it seems that this problem has been solved within branch and maybe was
> noted within bugzilla at ..., can anyone give me a hint to back- of
> fowardsport ...."
IMHO this step is not needed, if a not yet synced patch is
mentioned/attached to a bugzilla entry. The behavior you describe, using
the ml as a primitive bugzilla substitution, is just a waste of
development time and should be the exception. We should carefully handle
the time of other developers.
>
> > Open source is not about hacking only, it is
> >about developing quality software which is useful.
> >
>
> aren't bugfixes useful?!
Of course in general. But we are core developers and should follow
professional development rules and behavior. IMHO, we still have to
learn to adopt this behavior.
However, I would strongly recommend that we open bugzilla entries for
patches applied for one branch and which should also be applied in
another branch but have not yet. This would save us all a lot of time;
we do not have to search a big ml archive for possible forgotten
patches! That is waste of valuable time.
--
Rolf Kulemann
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: svn commit: r154188 - lenya/branches/BRANCH_1_2_X/src/webapp/lenya/usecase.xmap
Posted by Michael Wechner <mi...@wyona.com>.
Rolf Kulemann wrote:
>On Sat, 2005-02-19 at 14:16, Gregor J. Rothfuss wrote:
>
>
>>Michael Wechner wrote:
>>
>>
>>
>>>it's easy to keep track of them. Since it's an improvement one will
>>>notice anyway and hence it won't be forgotten if actually needed.
>>>
>>>
>>it is not. i just found a *another* case this week where a patch had not
>>been synced for months, in this case in the other direction.
>>
>>your "if actually needed" statement worries me. are you saying we should
>>have to re-discover each bug for each branch?
>>
>>
>
>If I find myself wasting hours doing this rediscovering, I would be
>really really annoyed.
>
nobody is saying that you or anyone else has to do this. Nobody is
forced to do further improvements. Improvements are voluntary!
It definitely makes sense to use bugzilla for this
and I apologize for not having done so far, but at the same time this
also what the mailing list is good for, e.g.
"it seems that this problem has been solved within branch and maybe was
noted within bugzilla at ..., can anyone give me a hint to back- of
fowardsport ...."
> Open source is not about hacking only, it is
>about developing quality software which is useful.
>
aren't bugfixes useful?!
> And a community is no
>vacuum cleaner.
>
>
hm?
Michi
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: svn commit:
r154188 - lenya/branches/BRANCH_1_2_X/src/webapp/lenya/usecase.xmap
Posted by Rolf Kulemann <ro...@apache.org>.
On Sat, 2005-02-19 at 14:16, Gregor J. Rothfuss wrote:
> Michael Wechner wrote:
>
> > it's easy to keep track of them. Since it's an improvement one will
> > notice anyway and hence it won't be forgotten if actually needed.
>
> it is not. i just found a *another* case this week where a patch had not
> been synced for months, in this case in the other direction.
>
> your "if actually needed" statement worries me. are you saying we should
> have to re-discover each bug for each branch?
If I find myself wasting hours doing this rediscovering, I would be
really really annoyed. Open source is not about hacking only, it is
about developing quality software which is useful. And a community is no
vacuum cleaner.
--
Rolf Kulemann
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: svn commit: r154188 - lenya/branches/BRANCH_1_2_X/src/webapp/lenya/usecase.xmap
Posted by Michael Wechner <mi...@wyona.com>.
Rolf Kulemann wrote:
>>No, but it will be re-discovered if necessary, or otherwise we could
>>just use bugzilla to keep track.
>>
>>
>
>Yep, have you recorded your last two?
>
>
>
no, but I agree that I should have done so.
Michi
--
Michael Wechner
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
michael.wechner@wyona.com michi@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: svn commit:
r154188 - lenya/branches/BRANCH_1_2_X/src/webapp/lenya/usecase.xmap
Posted by Rolf Kulemann <ro...@apache.org>.
On Sat, 2005-02-19 at 15:34, Michael Wechner wrote:
> Gregor J. Rothfuss wrote:
>
> > Michael Wechner wrote:
> >
> >> it's easy to keep track of them. Since it's an improvement one will
> >> notice anyway and hence it won't be forgotten if actually needed.
> >
> >
> > it is not. i just found a *another* case this week where a patch had
> > not been synced for months, in this case in the other direction.
>
>
> what patch? Isn't this why mailing lists and the community exists?
> To tell what could be improved and to give advice?
>
> >
> > your "if actually needed" statement worries me. are you saying we
> > should have to re-discover each bug for each branch?
>
>
> No, but it will be re-discovered if necessary, or otherwise we could
> just use bugzilla to keep track.
Yep, have you recorded your last two?
--
Rolf Kulemann
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: svn commit: r154188 - lenya/branches/BRANCH_1_2_X/src/webapp/lenya/usecase.xmap
Posted by Michael Wechner <mi...@wyona.com>.
Gregor J. Rothfuss wrote:
> Michael Wechner wrote:
>
>> it's easy to keep track of them. Since it's an improvement one will
>> notice anyway and hence it won't be forgotten if actually needed.
>
>
> it is not. i just found a *another* case this week where a patch had
> not been synced for months, in this case in the other direction.
what patch? Isn't this why mailing lists and the community exists?
To tell what could be improved and to give advice?
>
> your "if actually needed" statement worries me. are you saying we
> should have to re-discover each bug for each branch?
No, but it will be re-discovered if necessary, or otherwise we could
just use bugzilla to keep track.
Michi
>
>
--
Michael Wechner
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
michael.wechner@wyona.com michi@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: svn commit: r154188 - lenya/branches/BRANCH_1_2_X/src/webapp/lenya/usecase.xmap
Posted by "Gregor J. Rothfuss" <gr...@apache.org>.
Michael Wechner wrote:
> it's easy to keep track of them. Since it's an improvement one will
> notice anyway and hence it won't be forgotten if actually needed.
it is not. i just found a *another* case this week where a patch had not
been synced for months, in this case in the other direction.
your "if actually needed" statement worries me. are you saying we should
have to re-discover each bug for each branch?
--
Gregor J. Rothfuss
COO, Wyona Content Management Solutions http://wyona.com
Apache Lenya http://lenya.apache.org
gregor.rothfuss@wyona.com gregor@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: svn commit: r154188 - lenya/branches/BRANCH_1_2_X/src/webapp/lenya/usecase.xmap
Posted by Michael Wechner <mi...@wyona.com>.
Rolf Kulemann wrote
>>agreed, but please see my other email.
>>
>>
>
>Better no commits than commits which are not synced.
>
I strongly disagree. Please see my other email (form over function)
>Who keeps track of
>patches applied to one but not the other branch?
>
>
it's easy to keep track of them. Since it's an improvement one will
notice anyway and hence it won't be forgotten if actually needed.
Michi
--
Michael Wechner
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
michael.wechner@wyona.com michi@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: svn commit:
r154188 - lenya/branches/BRANCH_1_2_X/src/webapp/lenya/usecase.xmap
Posted by Rolf Kulemann <ro...@apache.org>.
On Sat, 2005-02-19 at 15:31, Michael Wechner wrote:
> Gregor J. Rothfuss wrote:
>
> > Rolf Kulemann wrote:
> >
> >> Better no commits than commits which are not synced. Who keeps track of
> >> patches applied to one but not the other branch?
> >
> >
> >
> > +1
>
>
> are you serious about that? Better do NOTHING and leave bugs stay than
> fixing and improving stuff.
>
> I am very confused by this!
>
> I would be really interested what reason/explanation for this kind of
> rule there is?
>
> The process wihtin an Open Source project is not like then one within a
> company where normally one person is setting the priorities, but also
> gives the time to do something and is responsible in the end.
>
> Again, an Open Source project is based on voluntarily contributions, no
> matter if someone is a contributor, committer, PMC member or board member.
>
> What if a contributor (not committer) is submitting a patch for one branch.
> Then this patch shouldn't be applied until someone else is contributing
> the same patch for the other branch???
>
> Heh?
However, it is important to pen bugzilla entries to keep track of
patches which should also be applied to another branch. I can not see
that this is the current practice, unfortunately.
--
Rolf Kulemann
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: svn commit: r154188 - lenya/branches/BRANCH_1_2_X/src/webapp/lenya/usecase.xmap
Posted by Michael Wechner <mi...@wyona.com>.
Gregor J. Rothfuss wrote:
> Rolf Kulemann wrote:
>
>> Better no commits than commits which are not synced. Who keeps track of
>> patches applied to one but not the other branch?
>
>
>
> +1
are you serious about that? Better do NOTHING and leave bugs stay than
fixing and improving stuff.
I am very confused by this!
I would be really interested what reason/explanation for this kind of
rule there is?
The process wihtin an Open Source project is not like then one within a
company where normally one person is setting the priorities, but also
gives the time to do something and is responsible in the end.
Again, an Open Source project is based on voluntarily contributions, no
matter if someone is a contributor, committer, PMC member or board member.
What if a contributor (not committer) is submitting a patch for one branch.
Then this patch shouldn't be applied until someone else is contributing
the same patch for the other branch???
Heh?
Michi
--
Michael Wechner
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
michael.wechner@wyona.com michi@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: svn commit: r154188 - lenya/branches/BRANCH_1_2_X/src/webapp/lenya/usecase.xmap
Posted by "Gregor J. Rothfuss" <gr...@apache.org>.
Rolf Kulemann wrote:
> Better no commits than commits which are not synced. Who keeps track of
> patches applied to one but not the other branch?
+1
--
Gregor J. Rothfuss
COO, Wyona Content Management Solutions http://wyona.com
Apache Lenya http://lenya.apache.org
gregor.rothfuss@wyona.com gregor@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: svn commit: r154188
- lenya/branches/BRANCH_1_2_X/src/webapp/lenya/usecase.xmap
Posted by Rolf Kulemann <ro...@apache.org>.
On Sat, 2005-02-19 at 14:41, Michael Wechner wrote:
> Rolf Kulemann wrote:
>
> >On Thu, 2005-02-17 at 21:46, michi@apache.org wrote:
> >
> >
> >>Author: michi
> >>Date: Thu Feb 17 12:46:37 2005
> >>New Revision: 154188
> >>
> >>URL: http://svn.apache.org/viewcvs?view=rev&rev=154188
> >>Log:
> >>thanks to Linczak, Jonathan W. the root is not doubled anymore when creating a document
> >>
> >>
> >
> >Should this patch also be applied for trunk?
> >
> >
>
> I haven't found the time to test it yet.
>
> >Please keep the branches in sync.
> >
> >
>
> agreed, but please see my other email.
Better no commits than commits which are not synced. Who keeps track of
patches applied to one but not the other branch?
--
Rolf Kulemann
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: svn commit: r154188 - lenya/branches/BRANCH_1_2_X/src/webapp/lenya/usecase.xmap
Posted by Michael Wechner <mi...@wyona.com>.
Rolf Kulemann wrote:
>On Thu, 2005-02-17 at 21:46, michi@apache.org wrote:
>
>
>>Author: michi
>>Date: Thu Feb 17 12:46:37 2005
>>New Revision: 154188
>>
>>URL: http://svn.apache.org/viewcvs?view=rev&rev=154188
>>Log:
>>thanks to Linczak, Jonathan W. the root is not doubled anymore when creating a document
>>
>>
>
>Should this patch also be applied for trunk?
>
>
I haven't found the time to test it yet.
>Please keep the branches in sync.
>
>
agreed, but please see my other email.
Thanks
Michi
--
Michael Wechner
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
michael.wechner@wyona.com michi@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org