svn - Subversion: Is there any good reason not to create a Tag from multiple revisions? -


i know possible, , there various ways it, there reason not create tag multiple revisions?

what proposing create program based on svnkit , jakarta poi reads list of build artifacts excel spreadsheet / csv file (a mix of java class files , other stuff) @ various svn revisions, creates tag out of it, , tag becomes next proposed release.

i approach because:

  1. we have documentation (a baseline if will) detailing going each release.

  2. it gives our release manager (without checking out head or having learn complicated things branching , merging)

  3. developers can check-in whatever want when want without being constricted such concept 'release window'. i.e. restricting developers checking in prior release.

i distrust approach because:

it feels i'm violating basic svn principles (although i'm not sure what).

it because of niggling doubt i'm putting idea out there people kick tires speak. guys think?

you're not violating svn principles doing this. tag not inbuilt subversion construct, convention people use aid build process. people want tags based off single revision, again convention. have situation code ship consists of historical versions of files current versions of others?

if approach works you, go it. however, avoid confusion used normal definition of 'tags', perhaps call directory else? "builds" perhaps?


Comments

Popular posts from this blog

javascript - Enclosure Memory Copies -

php - Replacing tags in braces, even nested tags, with regex -