On 3/16/06, Eric Walstad <[EMAIL PROTECTED]> wrote: > > Most of our guys use Windows, so installing fedora is going to be a > > problem for them - I may have to think about getting a LAMP > > installation for them under Windows (or convert them to OS-X ;) > I've not bothered setting up a Windows development box. I don't know how > hard/easy it is to do so.
I've helped set this up a couple of times now and it is easy enough. Every library/dependency of Django has an easy to find Windows installer (or generic Python setup-tools installer, which work in Windows), including Postgres 8. The Django development server works just in fine in Windows, too. > > > 2. svn looks like the right thing to use, and as I said in my reply to > > Julio, there's going to have to be some lateral thinking there to use > > it best advantage. We're currently using bugzilla for tracking > > (integrated into Zope and we weren't aware of trac at the time - that > > only came through django) but frankly, I hate it - it's written in Perl > > which means that only a few people can do anything with it, which means > > we don't do anything with it... > My thoughts exactly :) I would interject here and point out that a source control system is just like any other piece of software and that there are alternatives to explore. Personally, I'm a big fan of distributed source control sytems and would recommend Darcs (www.darcs.net) to anyone/everyone, particularly those new to source control as darcs is very easy to set up (one possibility: just set up normal SSH accounts with group access to your shared repository) and pick up using. I've also heard good things about Mercurial as well, which is actually written in Python. So, let me just annotate Eric's example with the Darcs session as well: > > ... > > My main concern is > > bringing the team up to speed with using version control (we thought > > that 'versions' in Zope would do the same thing - you'll know that it > > doesn't work like that Eric!) and getting used to working in a > > different way. > A typical coding session looks like: > - Open trac to see what the most critical bug/task is There is a Trac+Darcs branch if you want Trac, or there are other options like RT or Roundup (in addition to the Bugzilla you are already using). I've got a _very_ simple, expandable, Django-based issue tracker, even. > - type 'svn update' to get the latest code 'darcs pull' to grab the latest patches. With darcs you can pull from a centrally shared repository, or from any other repository (ie, if each coworker wants to share a read-only copy of their repo so that they can pull each other's "work in progress" patches to test and evaluate) > - code like mad until the issue is resolved or the task is > complete > - 'svn update' again in case other's have modified the same > file you were working on - svn will almost always merge > the changes or will identify a conflict it can't resolve With Darcs this update step isn't as necessary. > - 'svn status' to show what files you changed - good for > verifying you changed only what you think you changed `darcs whatsnew`, but, again, it isn't required. > - 'svn add|rm|mv some.file' 'darcs add|remove|mv some.file' > and/or "svn commit -m 'my log message'" to commit your > changes 'darcs record' Record gives a nice interactive 'whatsnew', allowing you to say yes/no to every change you make and record it as a patch, with a name (log message) and optional comment. Unlike 'svn commit', though, this doesn't automatically post the change to some central server. Instead, you can then "sit" on the patch and let others 'darcs pull' it from your repository, or you can 'darcs push' it to some other repo or even 'darcs send' it to some email address... Like I said, I would recommend checking out Darcs (or at least a distributed SCM) particularly if you are new to SCMs as the additional flexibility and relative ease of setup make the learning curve that much easier. -- --Max Battcher-- http://www.worldmaker.net/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
