Haha, understood . . . just subscribed to dev. I'm talking primarily about Exhibit, but also about Simile AJAX and Timeline. I guess I was just wondering whether you tend to be pretty strict about making sure all tests are passing after every commit to trunk or whether you're willing to break the code for a couple days to experiment with something. I'm trying to balance the priorities of contributing patches with minimizing downtime. ;)
I'll probably just do the prudent thing and try to use stable branches/tags in production and keep my playing around with trunk separate. Cheers, Pius On 12/15/06, Ryan Lee <[EMAIL PROTECTED]> wrote:
Pius A. Uzamere II wrote: > Great job on this suite of software . . . really awesome research you guys > are doing. I'm just curious how stable you keep the trunk. I'm going to > integrate some of the Simile modules into a production app and I was > thinking of simply checking your code out using svn externals > (automatically > updating whenever you update the trunk). Is this wise or would it be > better to checkout a particular release? Have you subscribed to our dev list? You'll get a better idea of the flow of code by watching commits go by. The stability really depends on which particular part of the repository you're referring to since each individual project generally has its own trunk/tags/branches and development cycle. It's really your sense of priorities - would you rather play catch up with every commit, or would you rather risk falling behind / only play catch up when a new feature/fix catches your fancy? On projects that may or may not see a lot of development, depending on the weather, phases of the moon, etc.? A better sense of the specifics of your plans might get you a more straightforward answer :) -- Ryan Lee [EMAIL PROTECTED] MIT CSAIL Research Staff +1.617.253.5327 http://simile.mit.edu/ _______________________________________________ General mailing list [email protected] http://simile.mit.edu/mailman/listinfo/general
_______________________________________________ General mailing list [email protected] http://simile.mit.edu/mailman/listinfo/general
