Hi Michelle, I added the wiki page with the up to date summary of the builder testing: http://wiki.fluidproject.org/display/fluid/Build+Scripts+Improvements+Notes,+Testing. We will be updating the chart as we go along.
Yura On Mon, Dec 14, 2009 at 5:40 PM, Colin Clark <[email protected]> wrote: > Hey Michelle, > > > On 14-Dec-09, at 4:39 PM, Michelle wrote: > >> The main problem is the difficulty in testing the changes properly. Yura >> and Laurel have been testing this afternoon however there is still a lot of >> testing that remains. We should put our testing and results on the wiki - >> Yura, would you be willing to do this? The quick summary is that we still >> need to test the daily build, the release builds and the custom build. There >> are several minor differences that we've noticed between the old and new >> builds for things we have already tested. The biggest difference is in the >> unminified builds where we now include a war file and we no longer include >> the json dependency files. I'm not sure if this is a bug or a feature. >> Thoughts? >> > > Does anyone have a wiki URL where these test results have been posted? > > As for your question about the minor build differences, I think it's > reasonable to include a war file in the non-minified builds, and to prune > out the dependency files. I think, in the long run, we may want to look at > the structure of these "source" builds and ensure that they provide > everything required to rebuild them into a minified release. This would > include the build scripts themselves, dependency files, and so on. But since > that's a large and separate task, I think it's reasonable enough to provide > symmetrical builds instead. > > I can understand an argument where we want to ensure that 1.1.2.1 build > products are 100% identical to those produced by the 1.1.2 build, but I > think even with these slight variations this is still a "no feature" > release. What do you think? > > > The one issue that we've found so far is that my changes to the Infusion >> build have broken the Engage build. This is actually not a blocker for the >> infusion builder release since we'll be branching for that release. It does, >> however, mean that I can't commit my patch into trunk until I get the Engage >> build going again. >> > > You can still commit your changes to the Infusion 1.1.2.x branch (that's a > lot of dots!), allowing us to continue with the release of Builder while > trunk and Engage stay slightly behind the curve for an extra day or two > until we update Engage's build. Seem reasonable, or am I missing some key > details? > > Colin > > --- > Colin Clark > Technical Lead, Fluid Project > http://fluidproject.org > > > _______________________________________________________ > fluid-work mailing list - [email protected] > To unsubscribe, change settings or access archives, > see http://fluidproject.org/mailman/listinfo/fluid-work >
_______________________________________________________ fluid-work mailing list - [email protected] To unsubscribe, change settings or access archives, see http://fluidproject.org/mailman/listinfo/fluid-work
