Am 13.03.2012 um 16:41 schrieb Ramsey Gurley:
On Mar 13, 2012, at 2:57 AM, Pascal Robert wrote:
A mechanism to help processing web resources. It is hard to use tools like LESS or JS minification with the current set of tools.
I think this means it would be cool to have a preprocessor in our build.xml files to minify js and process css stylesheets. I agree, that would be awesome. Surely someone has done this already. Perhaps that someone could post an example so we don't have to figure it out from scratch :-)
to minify js and css add this to your build.xml:
<target name="minify" if="yuicompress.available">
<echo message="Minification of CSS files." />
<apply
executable=
"java" dir=
"${dest.dir}" relative=
"true">
<fileset dir="${dest.dir}" includes="**/WebServerResources/**/*.css"/>
<arg path="${yuicompress.jar}"/>
<srcfile/>
<arg line="--charset"/>
<targetfile/>
<mapper type="identity"/>
</apply>
<replace dir="${dest.dir}" includes="**/WebServerResources/**/*.css" token=";}" value="}"/>
<echo message="Minification of JS files." />
<apply
executable=
"java" dir=
"${dest.dir}" relative=
"true">
<fileset dir="${dest.dir}" includes="**/WebServerResources/**/*.js"/>
<arg path="${yuicompress.jar}"/>
<srcfile/>
<arg line="--charset"/>
<targetfile/>
<mapper type="identity"/>
</apply>
</target>
though that should be done only for deployment (i.e. building Wonder with that would make debugging js code in Eclipse hard).
serious release engineering
I have a question about this myself. Now that we have an integration branch where all the new pull requests are going, what is the process where those changes filter through to master? For instance, prototype 1.7 landed on integration a while ago. It hasn't moved since. What am I to make of that? Is there a problem with it? Does someone not like it? Did it break someone's apps? Inquiring minds would like to know, even though that's just one example. There appears to be a lot of stuff going into integration but not coming back out. With no issue receiving comments (or patiently waiting), it's hard to know where things stand.
Up to now its working fine, switched from master to integration for development/deployment a while back and no problems.
Is the proper course of action to push to integration as well? I've got a branch coming that represents a couple of months worth of commits. I've tested things pretty thoroughly myself. Should it still be pushed to integration and then cherry picked? That's gonna be a lotta cherry pickin'. I also have my doubts that anyone's going to test it any more thoroughly than I have already.
That I think will have to be discussed yet how to proceed with all those commits waiting to be put on master. Perhaps there should be time frames where all commits to integration are halted and if no problems exists in integration and no one complains the integration branch is merged into the master making some sort of "release". After that new commits are pushed to integration and the game starts over.
Should I just consider integration the new master?
work on migration system
get db downgrades to work
DB downgrades will never work. A column, once dropped, cannot be undropped. This reminds me of an interesting article from thedailywtf. Usually those are haha funny, but this one was actually an interesting read.
Ramsey