note strat <p>Hello,</p> <p>in my current project (not a web app, system programming and automation), we use the following way to develop, test and do the roll out.</p> <p><b>CVS:</b> will soon be replaced by Subversion</p> <p><b>UML:</b> we chose the Rational ones from IBM, and TopCased as an Eclipse plug in for the developers who don't have licenses for the Rational stuff (only for documenting).</p> <p><b>Eclipse</b> (from [|YOXOS]) with EPIC for Perl support, an integrated CVS (soon SVN) client (is as easy as tortoise), perltidy for formatting, and a lot of eclipse templates. It wasn't easy for me to switch from emacs (my favorite editor) to eclipse, but using the same platform independent tool for all developers is a big pro in my eyes. We just evaluate [|Jazz] which looks very interesting.</p> <p><b>Coding Standards:</b> we use a subset of "Perl Best Practices" (those parts which make sense) and several enhancements</p> <p><b>Perl and add ons:</b> to get a standard environment, we use [|pkgsrc] for Perl, libraries and some applications</p> <p><b>Packaging:</b> we use RPM for Linux, InstallP for AIX (and soon MSI for windows) and developed a little tool who does the packaging for us. The roll out is done in several stages, from develop (2 servers) to test (8 servers), to acceptance/integration test and then into production (about 200 server). We use a lot of automatic tests for step one and two.</p> <p><b>Perl-Modules</b>: lot's of them, but a list of them might not be helpful for you :-)</p> <p><b>[|Bugzilla]</b>: for Bugtracking, and the eclipse plug in mylin to use most of its features from eclipse.</p> <p><b>Update</b>: I forgot bugzilla, and fixed some spelling errors...</p> <!-- Node text goes above. Div tags should contain sig only --> <div class="pmsig"><div class="pmsig-123953"> Best regards,<br/> perl -e "s>>*F>e=>y)\*martinF)stronat)=>print,print v8." </div></div> 704810 704810