Regarding http://www.projectsycamore.org/Sapling/Roadmap
Philip asked: "Can we keep features in their own branches so they can be rejected or accepted more appropriately? In the past we've had monolithic branches, like wikis, etc, but I think we should shy away from that as much as possible as time goes on. (Meaning we just move these over to the Sycamore version roadmap page, rather than have versions for the "unstable trunk" [sapling]?" I think this is a good time to discuss the future of Sycamore roadmaps, release schedules, and all the other project management tasks associated with (open source) software development. AD _______________________________________________ Sycamore-Dev mailing list [EMAIL PROTECTED] http://www.projectsycamore.org/ https://tools.cernio.com/mailman/listinfo/sycamore-dev
