On 2/23/12 3 :42AM, "Justin Mclean" <jus...@classsoftware.com> wrote:
>It's simple to do.
>1. Extra stuff is checked in making revision 1001
>2. The compiler is checkin making revision 1002
>
>To make baseline build you'd need to:
>1. Check out everything (you get full version 1002)
>2. Check out frameworks directory revision 1000
>
>A tag would make it a little easier in that you wouldn't have to know the
>revision numbers ie you would check out the frameworks directory via a
>tag name. You could also checkout frameworks directory based on date
>using the {YYYY-MM_DD} syntax. You don't even need to use the command
>line to do this as all these option are build into most SVN clients
>including subclipse in Flash Builder (right click on frameworks, select
>Team then "Select to other Tag/Branch/Revision...").
While conceptually this makes sense I'm not sure it will work in practice.
We have more stuff to go into frameworks like the automation classes and
some misc other files that weren't cleared by legal before. I know our
local version of frameworks/build.xml differs already.
Will there really only be one submit with extra (non-Adobe) stuff? It can
get pretty messy pretty fast if we have Adobe stuff, not-Adobe stuff,
Adobe stuff, not-Adobe stuff, etc interleaved. How would you tag the
release if it shouldn't include some/all of the new stuff?
Carol
