I think branching was mentioned because you thought about creating a stable and a development version (which I think is an important idea). Consider having a stable version and a development version in two branches. Then you can make lots of fixes to the dev version without affecting the stable version. On the other hand you can still easily fix small errors that don't break things in the stable version. Let it be a typo or some easy-to-fix bug.
This can be done without a revision control system, but it's probably handier using one. Though the real advantages I see are much easier testing of development versions and a better record about what has been done when and how – including code history. Regards, Markus On Oct 7, 12:58 pm, The Editor <[email protected]> wrote: > Actually, I'm not too keen on having divergent versions of BoltWire. I > don't mind individual customizations, but don't want to try and > maintain or support different strains. So I'd be more inclined to use > a desktop version if it would help me. I will take a look at Bazaar > though, and possibly set something up for experimentation. > > Cheers, > Dan > > > > On Wed, Oct 7, 2009 at 3:45 AM, Markus <[email protected]> wrote: > > > Maybe we should stop with the theory and just setup a revision control > > system. Of course, Dan will stick with his way of development and > > releasing. In parallel, Dan and all others good tinker with the new > > system and then decide if it is an improvement or not. > > > I am quite busy currently but that will probably change in some weeks. > > So if anyone wants to set it up... > > > Which one should we give a try? Subversion, Bazaar, Git? Personally I > > like Bazaar because it seemed very intuitive and easy to me when I > > used it. > > > Regards, Markus > > > On Oct 6, 6:54 pm, DrunkenMonk <[email protected]> wrote: > >> > Do you recommend any for windows? And does it allow you to easily zip > >> > up a version when you feel good about it. > > >> The export (or similar) command lets you extract a certain version (by > >> version or date). I think you can do the following with subversion and > >> the zip command (normally I would use tar for my own projects, not > >> zip, sp I'm not sure how helpful zip is) > > >> svn export <repository>/boltwire | zip <name>.zip > > >> otherwise you'd have to do: > > >> cd tmp > >> svn export <repo>/boltwire > >> zip boltwire boltwire.zip > >> rm boltwire > > >> > The thing that attracts me > >> > most is sometimes I go up a dead end trail and have to retrace my > >> > steps before trying something else. Not always 100% successful, but my > >> > software does have very good undo capabilities! > > >> While I've never had the excuse to use it, I like the branching > >> capabilites, where you can copy parts of the project into a branch, > >> deveolpe the branch seperate from other branches that may create other > >> bugs, and then patch in the branches into the main trunk when done. > > >> But the "sod this, give me what I hd yesterday at noon" functionality > >> is definitly the most used of subversions magic on my computers :p --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "BoltWire" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/boltwire?hl=en -~----------~----~----~----~------~----~------~--~---
