I know this is annoying for you guys. Checking it in is the hard part, actually, as there's a bunch of non-versioned files, likely crazy SVN breakage and manual merging (even for the branch itself), and so forth. It'll take me a good day to do the commit, but I'll try to get to it soon, especially now that there's interest in hacking --philip
On 5/18/07, Rottenchester <[EMAIL PROTECTED]> wrote: > There are a couple of bugs we're working in sapling that are claimed > to be fixed in the wikis branch. But, as I mentioned this morning, > none of the wikis code has been checked in. It seems like a waste > for us to go out and re-fix those bugs, and it is also a lost > opportunity to start to merge wikis and trunk. > > I don't want to be pesty - just because I'm ready to do something > doesn't mean that Philip should be. That said, it's been over a month > since wikis went live, so I want to start a discussion that I hope > will let us nail this issue down. Here are a couple points: > > 1. Any check-in is better than none. I don't think that wikis > changes need to be merged into trunk for a "good" check-in. I think > a check-in of wikis, warts and all, will be better than the situation > we're in. > > 2. A check-in will eliminate some of the mystery about the delta > between sapling and wikis. Though the goals of the two projects seem > to be different, my guess is that the common code between the two is > pretty large. > > 3. Getting wikis into trac and keeping it maintained there will > benefit wikis even if the merge is a long way off. When someone fixes > a sapling bug, they can at least see if that bug is in the wikis code. > > Anyway, I'm offering this up to try to start a constructive > conversation, and hope it's taken in that spirit. > _______________________________________________ > Sycamore-Dev mailing list > [EMAIL PROTECTED] > http://www.projectsycamore.org/ > https://tools.cernio.com/mailman/listinfo/sycamore-dev > _______________________________________________ Sycamore-Dev mailing list [EMAIL PROTECTED] http://www.projectsycamore.org/ https://tools.cernio.com/mailman/listinfo/sycamore-dev
