2009/6/22 Ian Boston <i...@tfd.co.uk>: >> - do we need to release both java and PHP impl together [1] in the >> future? > > IMHO, the actual release process was quick to execute, so if they are done > together, I think its almost optimized.
Yes it is, but IMHO optimization is not the point. We need to think about bug fix release with changes in a given impl and not in the other. >> Also, I propose to create a svn externals to manage the branch, ie >> \shindig\trunks pointing to both 1.0 (branch) and 1.1 (trunk) and also >> site/sandbox >> Since we have now a website, I think the final layout could be >> \shindig\site (moved for /trunk/site) >> \shindig\trunk >> \shindig\trunks (new) >> \shindig\branches >> \shindig\sandbox >> If no objection, I will process in 72h. > > Is this going to make the merge harder ? I don't think since the actual structure is preserved, and svn externals will be add. The migration is easiest too: all dev could work with their local working space and commit their changes. In a future, they could do a svn checkout from /trunks Cheers, Vincent
