Keeping branches in sync

[Michael Wechner <mi...@wyona.com>]

I recently did a few patches within 1.2.x but also within 1.4-dev, but 
didn't apply them within both branches for the following reasons:

1) I normally apply them where I find the problem and need it fixed 
(very egoistic ;-)

2) 1.4 is different from 1.2 and hence a patch cannot just be copied or 
maybe sometimes it could, but I want to make sure that this is really 
the case.
I normally do a clean and reinstall before I check in stuff to make sure 
that
I don't miss anything. This is a time-intensive thing and unfortunately 
I currently don't have so much time as I would like to have

3) 1.4 is sometimes broken and I don't want to check something in when I 
cannot really test it

So to summarize, it's not that I am lazy and think that someone else should
do the rest, but it's just that I don't have arbitrary time left. 
Nevertheless I don't think we should wait checking in patches and leave 
bugs, just because they should be applied within both branches at the 
same time. I think this would be quite unrealistic and deconstructive.

As soon as I will find time I will apply the patches to the other branch.

If somebody steps in between then this is great and very much appreciated.

I think it's important to know that all work is voluntarily and each of
us is trying it's best to fix and enhance things.

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