Where to start..
First and foremost, the changes you are contemplating are an absolute necessity for a growing organization as well as, in the end, deliver manageable projects in the long term. Common development environment configurations: 1. Speeds the ability of new developers to come up to speed as you have the opportunity to document your configuration. 2. Eases the ability to return to an archived project and be productive. 3. Facilitates uniform build scripts (for scripted builds which are really nice). The larger your projects, the more you will want more and more automation. 4. Facilitates collaboration. Subversion: Your developers don't have to have every line of code in every project. In our Subversion repository we have probably 75 different projects (Flex, Java, .NET) across our development teams and product groups. Each developer checks out whatever project they are working on at the time. For example, a typical Flex project for our group is built from 3-4 subversion projects. This sounds like a lot of work, but when you get to building shared libraries, you will easily see where this approach has benefits. Your biggest issue to deal with in advance is to develop the rules/discipline necessary to make the team work together. There is nothing worse than a developer that infrequently checks-in as the risk of collision and re-work is magnified as the time between check-ins increases. You have to approach SCM as a collaboration mechanism and set policies accordingly. This means that you must develop standards that deal with the process of software development unlike anything you have done before. Common Rules: * Designate a person to perform Build Master/SCM Owner tasks (tags, branches, merges) * Frequent Check-ins * Prior to a check-in, a developer MUST update to the current revision and perform flexuint/acid tests verifying that the inbound changes don't break the build. * A developer who has checked in code breaking the build must fix the build immediately (before going home) Depending on Internet Connections: Although it's hard to accomplish and keep up, I like having local web servers and app servers. If that is too problematic, most developers use a single service over and over meaning for a majority of the time, they could consume a local XML document. Figure the services aren't going to be "done" at the same point the Flex side is ready to consume them anyway. KFB From: [email protected] [mailto:[email protected]] On Behalf Of Link Mckinney Sent: Saturday, February 28, 2009 1:51 PM To: [email protected] Subject: [flexcoders] Multiple developer environment setup with subversion and all offsite We are currently looking to start using subversion for our flex application and other web applications and would like to get some feedback on how you would set our environment up. We all work from home, and we have a dedicated production/development server. It is currently only me who is developing all the web and flex applications, but my boss has told me we are getting way too busy now for just one developer. I have a local development environment that I develop and test locally, then when I am finished with my tasks given and want my boss to finally look and test my work, I upload it to the test server. When the test is completed, we then promote to the production server. My problem lies at, 1). if we go to multiple developers, then they would also have to set up their local environment like mine and keep our code in their environment. 2). If we created the remote developer server then you are really depending on your internet connection. if that goes then you cannot develop. But on the flip side, all of our code would rest on our development server and not in their environment. We currently use Flex Builder 3 and Dreamweaver. if we choose option 1 then this would be the developers requirements Flex Builder 3 with Tasktop connector for bugzilla and subversive for subversion ColdFusion 8.1 developer edition MYSQL 5.1 with schema that we provide Apache 2.2 if developer is on mulitple projects with us. I would like to get some input on how you would solve this problem. Thanks Link -- This message has been scanned for viruses and dangerous content by MailScanner <http://www.mailscanner.info/> , and is believed to be clean.
