On 2/22/12 11:36 PM, "Justin Mclean" <jus...@classsoftware.com> wrote:
> Hi,
>
> With a tag on the framework directory we can easily checkout the trunk before
> any changes that are made to it. We don't actually even need a tag a svn
> checkout -revision 1290843 will get the framework as it was initially donated
> by Adobe. If we did create a tag it would only be use to create a baseline
> build.There would be no need to either check anything into that branch or
> merge anything that I can see. I'm assuming here we create a branch of the
> frameworks directory not the whole repo.
>
> I don't think we need to create lots of branches in the whiteboard areas and
> then try merge back later once the full code been donated. That's just making
> things harder for ourselves and making the full repo a little on the large
> size.
>
> We are talking about minimal changes here that have absolutely no effect on
> the build on the unless you actually change the build files. (Unless we also
> go ahead with the changes to framework_build.xml.) Even with the locale files
> added the swc files produced via a build will be byte by byte identical.
>
> Am I missing something here?
>
> Justin
Let's say the SVN with history is rev 1000. You are about to commit rev
1001. Later we'll add in the compiler at rev 1002. To build parity, we
want 1000 and 1002, but not 1001. I don't think tags can do that, but I've
never used them.
I think Omar might be right. We create a single branch (not necessarily on
the whiteboard), you and others check in their changes there, later we merge
them in. Right after the parity release we want cut another release with
your changes and a few other changes in there so we'll integrate those
changes from the branch back to trunk.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
