[Rubycocoa-devel 347] wwdc + macosforge + branches

Zurück zum Archiv-Index

Laurent Sansonetti lsans****@apple*****
Fri Aug 11 04:48:56 JST 2006


Hi guys,

So I am right now at WWDC, along with Hisa-san, and we have been  
discussing about things.

First of all, but this should not be a surprise for you, RubyCocoa is  
bundled with Leopard. Apple is committed to make the bridge as stable  
as possible and support it in future releases of the OS. The key idea  
is to leverage Ruby at the same level of support as ObjC, providing  
everything to make developers happy to write full Cocoa-based  
applications in Ruby (this includes documentation, tutorials,  
integration with the Apple developer tools, etc...).

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.

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?

Thanks!
Laurent



More information about the Rubycocoa-devel mailing list
Zurück zum Archiv-Index