[mnet-devel] unifying development effort

[Bryce O'Whielacronx]

I've been thinking about the development process.  We have too small of a team 
to split development between different branches, because then people feel that 
their code is potentially going to waste, potentially bit-rotting, possibly 
even incompatible with code being developed on other branches.  For most of 
us, our primary motivator is social feedback, and developing on separate 
branches destined for separate releases is inimical to that.

I still believe that we have to support both evolutionary and revolutionary 
development efforts, simply because we have to have a current running version 
that works at least well enough to demonstrate the concept, and we also have 
to have the freedom to make up new ideas that are unhindered by old ideas.

However, we can do better about making both kinds of development happen on the 
same codebase, with the same people all cooperating together.

I think there won't ever be another branch as deep and difficult as the 
v0.6/v0.7 branch.  Both v0.7.0 and its successor will come from the same 
codebase, and will come from a unified development effort where everyone feels 
like they are working toward the same goals, and that the individual 
contributions are mutually supportive.

Regards,

Zooko

P.S.  I've started merging peerman onto v0.7 in a fairly non-disruptive way.



-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
mnet-devel mailing list
mnet-devel at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mnet-devel