Re: [flexcoders] Flex server Subversion
I made the same mistake when I first started working with SVN. Generally speaking you want to keep things in one repository if they are at all related. It's considerably easier to move things within a single repository than between different ones. ...paul On Dec 13, 2007 5:22 PM, DannyT [EMAIL PROTECTED] wrote: Thanks guys, feel much better about it all now :) Tom, why do you keep them all in the one repository and not setup different repositories for each project? Dan On 13/12/2007, Andrew Scott [EMAIL PROTECTED] wrote: There is no hard fast rules, but what best suits you. Here is what we do, and this applies mainly to more than 1 developer. If one developer then you can ignore the fact that you don't need to merge / sync code as much. 1) Create a repository with a trunk / branch / tag 2) Write code. 3) Sync with repository, and merge any changes. 4) then update changes from others if it is needed. The idea behind a stable repository, is that when someone else updates it will not break anything that they need to do. This is important to try to maintain as much as possible, not always applicable because bugs can and do happen but with great test coverage as unit testing etc, you can minimize this as much as possible. Any time you make your product live, and start to work on another version it is best to branch the code. This is basically making a snapshot of the current stable released version. The idea is that if you then begin on version XX.YY then you can easily switch between versions to fix enhance or what ever you need to do. This has got be the most important feature we use, the ability to switch between a branch and trunk version at will, and have the ability merge / sync code between them in needed. On 12/13/07, DannyT [EMAIL PROTECTED] wrote: I've seen a couple of threads on this but not enough for a definitive conclusion. I'm trying to define a standard practice for source controlling a flex and back-end project (namely flex - remoting - .net ( - sql?) Do people tend to treat their server-side projects as a separate project in a separate repository? With everything in the one repository you can keep local compilation consistent and check-in build scripts, however by splitting up into multiple projects you're keeping flexibilty and managability by not bloating your repository. I guess it'll come down to preference but was just wondering what others are doing, as a general rule our developers currently will be dealing with both client side and server side projects but down the line i'd like to see clearer separation of roles. Any thoughts or practices people can throw in would be much appreciated. Dan -- http://danny-t.co.uk -- Senior Coldfusion Developer Aegeon Pty. Ltd. www.aegeon.com.au Phone: +613 8676 4223 Mobile: 0404 998 273 -- http://danny-t.co.uk
Re: [flexcoders] Flex server Subversion
On Thursday 13 Dec 2007, DannyT wrote: Trunk/client/ Trunk/server/ Us too, except we have many separate client/server apps, so at the mo we've got: /trunk/projectA-client /trunk/projectA-server /trunk/projectB-client /trunk/projectB-server /trunk/shared-client /trunk/shared-server /trunk/flexlib which is quite a lot of items in the SVN root. I wish we'd put clients and servers together: /trunk/projectA/client /trunk/projectA/server /trunk/projectB/client /trunk/projectB/server /trunk/shared-client /trunk/shared-server /trunk/flexlib -- Tom Chiverton Helping to quickly e-enable innovative technologies on: http://thefalken.livejournal.com This email is sent for and on behalf of Halliwells LLP. Halliwells LLP is a limited liability partnership registered in England and Wales under registered number OC307980 whose registered office address is at Halliwells LLP, 3 Hardman Square, Spinningfields, Manchester, M3 3EB. A list of members is available for inspection at the registered office. Any reference to a partner in relation to Halliwells LLP means a member of Halliwells LLP. Regulated by The Solicitors Regulation Authority. CONFIDENTIALITY This email is intended only for the use of the addressee named above and may be confidential or legally privileged. If you are not the addressee you must not read it and must not use any information contained in nor copy it nor inform any person other than Halliwells LLP or the addressee of its existence or contents. If you have received this email in error please delete it and notify Halliwells LLP IT Department on 0870 365 2500. For more information about Halliwells LLP visit www.halliwells.com. -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links * To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ * Your email settings: Individual Email | Traditional * To change settings online go to: http://groups.yahoo.com/group/flexcoders/join (Yahoo! ID required) * To change settings via email: mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] * To unsubscribe from this group, send an email to: [EMAIL PROTECTED] * Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
Re: [flexcoders] Flex server Subversion
There is no hard fast rules, but what best suits you. Here is what we do, and this applies mainly to more than 1 developer. If one developer then you can ignore the fact that you don't need to merge / sync code as much. 1) Create a repository with a trunk / branch / tag 2) Write code. 3) Sync with repository, and merge any changes. 4) then update changes from others if it is needed. The idea behind a stable repository, is that when someone else updates it will not break anything that they need to do. This is important to try to maintain as much as possible, not always applicable because bugs can and do happen but with great test coverage as unit testing etc, you can minimize this as much as possible. Any time you make your product live, and start to work on another version it is best to branch the code. This is basically making a snapshot of the current stable released version. The idea is that if you then begin on version XX.YY then you can easily switch between versions to fix enhance or what ever you need to do. This has got be the most important feature we use, the ability to switch between a branch and trunk version at will, and have the ability merge / sync code between them in needed. On 12/13/07, DannyT [EMAIL PROTECTED] wrote: I've seen a couple of threads on this but not enough for a definitive conclusion. I'm trying to define a standard practice for source controlling a flex and back-end project (namely flex - remoting - .net ( - sql?) Do people tend to treat their server-side projects as a separate project in a separate repository? With everything in the one repository you can keep local compilation consistent and check-in build scripts, however by splitting up into multiple projects you're keeping flexibilty and managability by not bloating your repository. I guess it'll come down to preference but was just wondering what others are doing, as a general rule our developers currently will be dealing with both client side and server side projects but down the line i'd like to see clearer separation of roles. Any thoughts or practices people can throw in would be much appreciated. Dan -- http://danny-t.co.uk -- Senior Coldfusion Developer Aegeon Pty. Ltd. www.aegeon.com.au Phone: +613 8676 4223 Mobile: 0404 998 273
Re: [flexcoders] Flex server Subversion
Thanks guys, feel much better about it all now :) Tom, why do you keep them all in the one repository and not setup different repositories for each project? Dan On 13/12/2007, Andrew Scott [EMAIL PROTECTED] wrote: There is no hard fast rules, but what best suits you. Here is what we do, and this applies mainly to more than 1 developer. If one developer then you can ignore the fact that you don't need to merge / sync code as much. 1) Create a repository with a trunk / branch / tag 2) Write code. 3) Sync with repository, and merge any changes. 4) then update changes from others if it is needed. The idea behind a stable repository, is that when someone else updates it will not break anything that they need to do. This is important to try to maintain as much as possible, not always applicable because bugs can and do happen but with great test coverage as unit testing etc, you can minimize this as much as possible. Any time you make your product live, and start to work on another version it is best to branch the code. This is basically making a snapshot of the current stable released version. The idea is that if you then begin on version XX.YY then you can easily switch between versions to fix enhance or what ever you need to do. This has got be the most important feature we use, the ability to switch between a branch and trunk version at will, and have the ability merge / sync code between them in needed. On 12/13/07, DannyT [EMAIL PROTECTED] wrote: I've seen a couple of threads on this but not enough for a definitive conclusion. I'm trying to define a standard practice for source controlling a flex and back-end project (namely flex - remoting - .net ( - sql?) Do people tend to treat their server-side projects as a separate project in a separate repository? With everything in the one repository you can keep local compilation consistent and check-in build scripts, however by splitting up into multiple projects you're keeping flexibilty and managability by not bloating your repository. I guess it'll come down to preference but was just wondering what others are doing, as a general rule our developers currently will be dealing with both client side and server side projects but down the line i'd like to see clearer separation of roles. Any thoughts or practices people can throw in would be much appreciated. Dan -- http://danny-t.co.uk -- Senior Coldfusion Developer Aegeon Pty. Ltd. www.aegeon.com.au Phone: +613 8676 4223 Mobile: 0404 998 273 -- http://danny-t.co.uk
[flexcoders] Flex server Subversion
I've seen a couple of threads on this but not enough for a definitive conclusion. I'm trying to define a standard practice for source controlling a flex and back-end project (namely flex - remoting - .net ( - sql?) Do people tend to treat their server-side projects as a separate project in a separate repository? With everything in the one repository you can keep local compilation consistent and check-in build scripts, however by splitting up into multiple projects you're keeping flexibilty and managability by not bloating your repository. I guess it'll come down to preference but was just wondering what others are doing, as a general rule our developers currently will be dealing with both client side and server side projects but down the line i'd like to see clearer separation of roles. Any thoughts or practices people can throw in would be much appreciated. Dan -- http://danny-t.co.uk
Re: [flexcoders] Flex server Subversion
Well that's reassuring as I use: Trunk/client/ Trunk/server/ Can you explain what you mean by keep the flex project files separate from the source AND keep them out of subversion? Also i've read about not including non-embedded files in output directory, which sounds logical to me, do you do this? Cheers, mucho appreciated Dan On 13/12/2007, Mike Chabot mchabe I have it set up as this: /trunk/FlexSource/ /trunk/WebSite/ I keep Flex project files separate from the source code and keep the project files out of Subversion. The setup has been working well for me. The people on the project that have nothing to do with Flex can just check out the /trunk/WebSite/ folder. Someone else I know has their's set up like this: /trunk/ui/ (flex code) /trunk/services/ (java web services that supply flex) -Mike Chabot On Dec 12, 2007 8:21 PM, DannyT [EMAIL PROTECTED]danmoov2%40googlemail.com wrote: I've seen a couple of threads on this but not enough for a definitive conclusion. I'm trying to define a standard practice for source controlling a flex and back-end project (namely flex - remoting - .net ( - sql?) Do people tend to treat their server-side projects as a separate project in a separate repository? With everything in the one repository you can keep local compilation consistent and check-in build scripts, however by splitting up into multiple projects you're keeping flexibilty and managability by not bloating your repository. I guess it'll come down to preference but was just wondering what others are doing, as a general rule our developers currently will be dealing with both client side and server side projects but down the line i'd like to see clearer separation of roles. Any thoughts or practices people can throw in would be much appreciated. Dan -- http://danny-t.co.uk -- http://danny-t.co.uk
Re: [flexcoders] Flex server Subversion
I keep the Flex source in subversion and the Flex project settings out. Source being .as and .mxml. Project settnigs being .project and .settings. Project settings is clearer than project. Yes, I uncheck the non-embedded option when working with source control. -Mike Chabot On Dec 12, 2007 9:17 PM, DannyT [EMAIL PROTECTED] wrote: Well that's reassuring as I use: Trunk/client/ Trunk/server/ Can you explain what you mean by keep the flex project files separate from the source AND keep them out of subversion? Also i've read about not including non-embedded files in output directory, which sounds logical to me, do you do this? Cheers, mucho appreciated Dan On 13/12/2007, Mike Chabot mchabe I have it set up as this: /trunk/FlexSource/ /trunk/WebSite/ I keep Flex project files separate from the source code and keep the project files out of Subversion. The setup has been working well for me. The people on the project that have nothing to do with Flex can just check out the /trunk/WebSite/ folder. Someone else I know has their's set up like this: /trunk/ui/ (flex code) /trunk/services/ (java web services that supply flex) -Mike Chabot On Dec 12, 2007 8:21 PM, DannyT [EMAIL PROTECTED] wrote: I've seen a couple of threads on this but not enough for a definitive conclusion. I'm trying to define a standard practice for source controlling a flex and back-end project (namely flex - remoting - .net ( - sql?) Do people tend to treat their server-side projects as a separate project in a separate repository? With everything in the one repository you can keep local compilation consistent and check-in build scripts, however by splitting up into multiple projects you're keeping flexibilty and managability by not bloating your repository. I guess it'll come down to preference but was just wondering what others are doing, as a general rule our developers currently will be dealing with both client side and server side projects but down the line i'd like to see clearer separation of roles. Any thoughts or practices people can throw in would be much appreciated. Dan -- http://danny-t.co.uk -- http://danny-t.co.uk
