The first two items aren't an issue. The third won't be once 0.8 is fully implemented and we're ready for our first release, and we won't commit to not changing anything before then -- we've got to get it right if we want to have software that's useful. If you have an issue with that, you may want to wait until our first release. We're not intentionally breaking anything, but we're also not going to go forward with a bad design when we haven't had any official releases yet.
That said, define "stable". We have strict requirements on code quality (see our style guides at http://cwiki.apache.org/SHINDIGxSITE), but that doesn't mean that there won't be lots of internal change. We're confident enough in the quality of our project to use it to run the entire OpenSocial deployment at Google. We're much more cautious about breakages at integration points, of course, but the internal code changes a lot. That's why we require thorough tests. On Sat, Jun 14, 2008 at 4:24 AM, Rajdeep Dua <[EMAIL PROTECTED]> wrote: > Are we having a process followed while check-ins are made to make sure > > 1. Check in by developer in one language doesn't break something for the > other language., this is especially important as there are some common > files > shared between PHP and Java version > 2. Make sure that the unit tests are run for both the versions are run > before a check-in is made > 3. Have stable source code tree tagged and documented for reducing > developers efforts in trying to build and run an unstable version. > > Thanks > Rajdeep >
