Laurent Sansonetti
lsans****@apple*****
Sat Aug 12 18:08:33 JST 2006
On Aug 10, 2006, at 2:34 PM, Jonathan Paisley wrote: > On 10 Aug 2006, at 20:48, Laurent Sansonetti wrote: > >> So I am right now at WWDC, along with Hisa-san, and we have been >> discussing about things. > > Cool! > > A quick reply to your points below: > >> Another thing that has been announced is the macosforge.org website. >> This is a community effort to host MacOS-related projects that has >> been created after the opendarwin.org shutdown. It provides SVN, >> trac, >> web hosting, shell access, and the possibility to compile for >> different architectures. We will have several Xserve machines to host >> everything. Recently Jonathan converted the CVS repository to SVN >> which is great. Note that it's just a suggestion; we have this >> website, it has all the things we need (if we need more things this >> is >> also possible to install more stuff); it should be way faster than >> SF.net. If all of you would like to move to macosforge.org it's >> fully >> possible. > > I think this would probably be a good thing. I'd like to see the web > site, documentation, faq, etc consolidated in one place. > Excellent. I talked to the macosforge people and they would be happy to host RubyCocoa. They are right now working on enlarging the hardware infrastructure, but we should probably be able to do something next week(s). If everyone is happy with that I will perform the necessary steps in order to start the migration. >> Finally, there is this "apple-unstable" branch. The version of >> RubyCocoa in Leopard has been produced from this branch. I think it >> would be great to start merging the content of this branch into >> trunk. >> I have a long list of things in my TODO list for RubyCocoa that I >> will >> work on in the next weeks (I will BTW write an e-mail about this >> soon). I propose that we either merge changes from apple-unstable >> into >> trunk, or that we rename apple-unstable into trunk (and rename trunk >> into something else). Having 2 different branches is a mess to >> maintain, I am not against having a stable and unstable branch >> though. >> Any idea about solving this? > > I think it'd be good to merge the branches. I've recently committed > an upgrade to trunk for a .xcodeproj instead of .pbxproj project > format, including eliminating the autogenerated project file. This > means we can now make changes to the project in Xcode without the > headache of converting back to the *.in file. > Yes I saw that, this is a good news thanks! I will merge these changes to the apple-unstable branch, I wonder if it would be possible to do the same for Xcode templates (did not investigate yet). > As for future development, I'd probably go for the new-development-on- > trunk approach, along with experimental features being developed on > branches (pretty much as you have done for apple-unstable, except I'd > like branches for smaller features). > Sounds fair enough. > I've currently got some work on the threading patches in my local SVK > repository, where I've cleaned up the ruby interpreter patch to be > more general (not rubycocoa-specific). Once this has been bugfixed > and tested, I'll push it into the svn repository. > Excellent. Lots of people are concerned by this threading issue. Please send me a pointer to your latest patches, I will now check this out in priority, and make sure they will be incorporated in Leopard. > Hope you're enjoying WWDC. :) > Thanks, this has been a very busy week, and I could discuss with several people interested about RubyCocoa in producing commercial applications. This is a great news I think :) Cheers, Laurent
