in reply to Re: How to structure your svn/svk repository
in thread How to structure your svn/svk repository

Tagging should be done early and often, especially as tagging is O(1) in SVN. I generally tag every 4-10 commits in my CPAN projects

I'm curious what the point of a tag is if you're tagging this often? Or is it just a marker for "all tests pass"?

Actually - I guess this depends on how often you commit... I tend to commit many times per-hour (pretty much every time I go from a test failing to all tests passing).

  • Comment on Re^2: How to structure your svn/svk repository

Replies are listed 'Best First'.
Re^3: How to structure your svn/svk repository
by dragonchild (Archbishop) on Oct 10, 2005 at 19:05 UTC
    Lots of reasons. Once a feature has been added or a bug fixed, I'd like to tag that. Also, my point releases tend to be small, which means I shouldn't be having to add a lot of tests, which means 4-10 commits may very well be the 4-10 new tests I added and made pass.
    My criteria for good software:
    1. Does it work?
    2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?
[reply]

In Section Seekers of Perl Wisdom