On Sun, 16 Jan 2005 07:21:21 -0500, Ted Husted wrote: > * I'd suggest that we tag each subproject release before it is > rolled. Ideally, the tag should identify exactly what goes into a > given subproject release.
Which implies that the head for each subproject is not required to build against the head of every other subproject (on the same platform). For example, right now, C# DataMapper 1.5.0 depends on DataAccess 1.1.0. Theoretically, we might decide to make some changes for DataMapper 1.6.x, which might not be compatible with DataAccess 1.1.x. We might want to get a release of DataMapper 1.6.0 out first, and then bring out an updated DataAccess release. After all, not everyone uses DataAccess. Later, when we get to it, we could then bring out an an updated NPetShop release that uses the new "best available" DataMapper and DataAccess releases. In the meantime, the old NPetShop will work just fine with the old DataAccess package, which works just fine with the old DataMapper package. I'm a little sensitive to this issue because we had such great problems during the Struts 1.1 "death march". We had to get all the "subprojects" just right before releasing anything. I just want to be sure that we have a project structure that would allow us to do one thing at a time. Of course, Team iBATIS has been doing this all along. For example, the documentation is not re-released just because a new SQL Mapper ships. Ditto for JPetstore. I just want to make sure we stay that course. -Ted.
