[WEBSITE] I've checked-in a starter website to the incubator SVN. It's rudimentary, but I wanted to get the ball rolling.
* http://incubator.apache.org/ibatis Next, I'd like to revamp it to work more like the logging.apache.org site, where there is a list of subprojects, and an area for each. Of course, we would also add the online version of the documentation and JavaDocs from ibatisnet.sf.net and ibatis.com, so that people can browse as much as possible online. We can also go ahead and setup a bylaws page by cribbing from other projects. I can continue setting up the site in "lazy" mode, which means I'll post things and copy the SVN changelogs here, so people can review the progress and question any changes. If you see anything you don't like, please don't hesitate to bring it up here. Of course, we would also want the Forrest sources for the site checked into our own Apache repository, when it is setup. For now, I checked it into the wush.net repository under "site". There are two ways to update the Apache websites. One is to check a working copy of the site into the repository and then ssh into the server and check it out. The SVN update can also be automated as a chron job, so that it is automatically refreshed on a regular basis. (Or triggered by a commit.) The other way is to scp a working copy to the server. For now, I'm using scp, but we might want to move to the svn-update approach later. [REPOSITORY] We discussed the SVN infrastructure on another thread, but I wanted to pick it up here before we do the conversion. Subversion is very flexible, and we can set things up a number of different ways. The CVS conversion utility will import the ibatisdb CVS like this: [cvs-module] .\branches .\tags .\trunk where the main line of development is trunk. This layout works well in practice, and it is familiar to many teams. What we are doing in Struts is putting the subprojects (including "core") at the root of the repository. Each subproject then has its own set of branches, tags, and trunk folders. (Or at least trunk, leaving room for the others if needed.) For Struts, we're trying to make each deliverable a subproject, with it's own release cycle. The proposed plan is to then aggregate subprojects into a Linux-style distribution. The Struts 1.3.0 distribution might be composed of (say) * Struts-Core 1.0.4 * Struts-Tags 1.0.0 * Struts-Extras 1.0.1 * Struts-Apps 1.0.5 We started moving toward the same sort of thing with the iBATIS.NET releases. We released the core, documentation, tutorial, and petshop applications separately. I think we could float a vote and mark these all GA now. (We could do this on SF.NET, since the code has not been checked-into Apache yet.) The next step might be to assemble the four GA releases into an iBATIS.NET 1.0.0 distribution. (Which could just be a ZIP file of the ZIP files.) In our own case, if we count the website, it looks like we have three root subprojects: /site /java /cs Site only has one deliverable (the top-level of the website), and so it would have trunk, et al, directly beneath /site ./trunk ./branches (if and when needed) ./tags (if and when needed) Java and cs have multiple deliverables (core, pet-app, dao, site), each of which should have their own trunk. /java ./core ../trunk ../branches ../tags ./dao ../trunk ./jpetstore ../trunk ./site (documentation) ../trunk /cs (ditto, expect that /npetshop replaces /jpetstore) Ultimately, I believe we might want a fourth subproject, for the DataMapper specification, especially if we start a PHP version. [PHP] I went to some PHP5 presentations at ApacheCon, and it's looking quite good. The XML libraries are *very* much enhanced, and it's essentially an OOP language now. iBATIS.php is something I'd like to work on in my "spare" time, if anyone else is interested. [MONO] I also went to a very cool presentation on Mono, which is now ready-for-primetime <http://www.mono-project.com/about/index.html >. The founder, Miguel de Icaza, gave one of our keynote addresses. Thanks to Novell, ASP.NET is no longer the dark-side, but is fast becoming the brightest light in open source. The core compilers are under GPL, but other parts may be moving to the Apache license. I imagine we want to pursue Mono certification for iBATIS.NET, and I'll be looking into that. [WUSH.NET SVN] Meanwhile, Gilles and I might want to refactor our wush.net SVN repository to mirror what we would have at Apache. Right now, we have everything at the root, so we'd want to create a /cs folder and move everything under that, and then create a "trunk" subdirectory for each deliverable, and move what we have under that. If we do that now at wush.net, it will mean less churn later when we are at Apache, and the changelog is being archived. [SF.NET CVS] How do we stand with handing the SF.NET CVS module over to infrastructure? ApacheCon and the Thanksgiving holiday are past, so work schedules should be getting back to normal. (At least mine is.) -Ted.
