For phase one this openness in communication, I would like to open the
discussion to strategies for working together. My interest is how to
deal with the notion of overlapping yet non-identical goals.
As a case study, let's look at deployment and developer preferences
for stability and
I agree with your analysis about slow deployment updates versus fast
community cycles.
In my view, there are two alternatives:
* We can slow down a little the Sugar cycle, may be doing one release by
year,
but I am not sure if will help. The changes will take more time to go to
the users?
If a
