Steve Bennett wrote:
On 12/31/06, Rob Church <robchur(a)gmail.com>
wrote:
If you're suggesting that we need to start
asking for permission
before we commit every single improvement to the software, then you
can forget it; a lot of them have to be done to make the site more
stable.
Asking permission? No. But the current situation looks to me like:
1) Developers randomly without any warning make unannounced changes
that affect users.
2) CSS and Javascript hackers randomly without any warning make
unannounced changes that affect users.
3) Users get peeved due to their feeling of powerlessness, and not
knowing any better, blame developers or CSS/Javascript hackers at
random.
4) Developers consider this unfair.
How do you think this can be improved?
one could introduce a RTC (review then commit) process instead CTR,
whereas one could do the review on a "staging branch" in order to
be more efficient.
I am a developer myself and I also would prefer to commit every time
I do a change and consider it good, but I had to come to realize that
software in general is for people using it and hence the user is king/queen
and all good intentions are worthless if such a gap arises.
Just my 2 cents
Michael
--
Michael Wechner
Wyona - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
michael.wechner(a)wyona.com michi(a)apache.org
+41 44 272 91 61