Why would we try this approach as opposed to the one Jeremy proposed,
i.e. moving what is already in sandbox to a branch or even trunk?
Since there are a number of initiatives people are already working on
in the sandbox codebase (e.g. Spring support, deployment,
conversations, data binding, OSGi support, support for new Java C&I
annotations, support for pluggable annotations) it is seems that
making improvements to that according to scenarios people are
interested in will be a nice way to move things forward involving as
many as possible.
Jim
On Jul 3, 2006, at 4:45 AM, ant elder wrote:
On 6/30/06, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
<snip/>
2. Stage the assembly of our M2 runtime.
I propose that we start a fresh stream for M2 and build the runtime
through
baby steps, in parallel with the scenario work. This will get our
community
members involved in building the runtime together and will lead to
a wider
knowledge base that makes it possible to quickly implement new
functionality
in the future. It will also build a community knowledge base that is
ready to
help new community members come on board quickly.
This approach appeals to me. Could we just give it a try for a
little while
when everyone is back on Wednesday? If it doesn't work out then all
the
other code will still be available in SVN to try another approach.
...ant
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
