> I'm not sure why we would merge changes from head onto an old branch.
OK, let's say that I create and want to commit a new matcher that we intend
to use in both v2.1.5 and v3.0. Where do I put it, and how do I get it into
both builds?
> Scope is large, or at least could be.
Once we've brainstormed the what-ifs, we can look at what we need to fulfill
functional requirements, e.g., those from Brian, and try to prioritize and
drive our development from what we need to accomplish (within the constraint
that volunteers will work on what is fun for them anyway).
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
