Ok, one more before I will actually shut up about this: My point is that if I get a working copy from the tag, I don't get the updated Mustella tests. That means that if I run the Mustella tests that comes with the code from the tag, I get failures. I don't want failures on an RC. In order to 'fix' those failures, I have to get another working copy, this time from the 'release' or 'develop' branch, and maybe - I'm not sure if this will work - copy-paste the Mustella directory from that working copy to the working copy I got from the tag. That means I have to 'change' the RC to test the RC, thereby losing the chain of evidence, as it were.
EdB On Mon, Oct 14, 2013 at 10:16 AM, Justin Mclean <jus...@classsoftware.com> wrote: > Hi, > >> Procedurally, I don't think you can cherry pick parts of the code to >> get something that 'works'. > And cherry picking is a painful to do anyway, I'd like to avoid it if we can. > >> I think that you should be able to go to git, say "give me the code as it >> was when we cut RC1" > That exactly what you can do - the source release package contents exactly > what was tagged with "apache-flex-sdk-4.11.0RC1". > > That even includes the flex-sdk-description.xml that was created as part of > the compile process (check the version/date in it) :-) > > What we may not be doing is testing that source release or tag in Jenkins CI. > That's may actually be hard to do as in this case it needs the tagged code > plus the updates to the tests, but no other updates if you wanted to be > really picky. > > I think Alex run the tests against the source release/RC1 tag not the latest > in the release branch and he would of updated the tests which are not part of > the source release. > > Thanks, > Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
