[os-infrastructure] State of the onion

[Joe Abbate]

Hi Alex,

Alex Hanshaw wrote:
> A tag is a copy. If you pull the take and make changes you create a
> branch.
> So it's not possible to pull a build to a level that reproduces a
> problem and submit a change in that build. Once a fix is identified a
> separate checkout from the actual code line has to be pulled and the
> change merged from the tag-checkout into the new build (where you can
> not confirm that
> intermediate changes have not invalidation the code solution in some
> way).
>   

If I do a svn checkout of a tag, I get in my build area all the files 
that were part of the tag.  If I have done an svn update in my build 
area and it's at revision 1234 and then I pull the tag for release 
9.2.0.132, and that tag has say dmfrcp.c at revision 1212, then the 
dmfrcp.c in my build area will be updated to match that revision.  A tag 
is a snapshot of what existed in the build area of whoever created the 
tag (just like a Piccolo label).  I can therefore rebuild from the tag 
and it should be identical to what was released when it was tagged.  If 
I then make a fix to dmfrcp.c and I commit then it will become part of 
say revision 1245, and assuming my build area was tracking branch 
2006r3, it would become part of that branch.  I can then do an svn 
update again to keep on working from head revs.

Joe