One thing to consider, as well, is the planned development & release
cycle going forward. Will eCos go back to a periodic, stable release
cycle (where the source-controlled code is considered relatively
unstable), or continue with occasional major releases, where most people
access the head of the development tree? I ask, because I would like to
see a way that we could provide for multiple developers to collaborate
on a new feature, or a way to distribute an "experimental" package for
test and comment before committing it to the main trunk.
Currently, it can get difficult e-mailing patches back and forth, and
this is exactly the problem that source control systems solved for us.
Frank
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
