Hi, In the SableVM project, all new feature development is done in sandboxes. This helps maintaining a robust trunk (as much as is possible). My experience is that this works well. Maybe you could do the same in Harmony. Isn't there already some "sandboxes"?
It might or might not work well here, though. In SableVM, bugs are not usually reported against sandboxes. In contrast, in Harmony, almost everything is done through JIRA, including patch submission... Etienne Weldon Washburn wrote: > On 11/4/06, Alexei Fedotov <[EMAIL PROTECTED]> wrote: >> So my suggestion is to create separate branches for new features which >> could be merged into the main branch when mature enough to achieve an >> appropriate level of stability. What do you think? > > As much as I hate it, I don't know how to avoid branching. Also, we > probably need some sort of JIRA coding to reflect which branch has which > patches. -- Etienne M. Gagnon, Ph.D. http://www.info2.uqam.ca/~egagnon/ SableVM: http://www.sablevm.org/ SableCC: http://www.sablecc.org/
signature.asc
Description: OpenPGP digital signature
