2009/4/19 Chris Chabot <[email protected]>: > Hey Vincent, > > Instead of enjoying the sunny sunday weather, I'm knee deep in trying to get > server sided template rendering done in php-shindig, which is being a > complete pain in the behind, and instead of spending my weekend on that I'm > spending my time testing a release procedure that almost everyone agreed > with probably isn't the best solution for php...
Yes surely not the best solution for php but a solution to unify the release process for both java and php... IIRC the issues were: * make-release script doesn't yet sign php tarball to respect ASF rules. * how to deploy the php tarbals on r.a.o? As I already said, the release process doc could be changed to include different steps for the php part. It is the main goal of this thread :) > I'm sorry but the amount of time I have left to go and learn maven and > hudson configurations is a negative number. I am willing to help you for the Maven part :) > Can't you just turn that lineEnding off for me, mail me a simple command or > 2 I have to run on the shindig-1.0.x branch to produce the release tarbals > so I can quickly test them? Of course! So I reverted the tag and modified the branch to add your requirements. Note that I didn't yet deleted artifacts in r.a.o cd 1.0.x-incubating mvn clean install cd assembly mvn clean install To help you, the generated php tarbals are: http://people.apache.org/~vsiveton/shindig-php/ HTH Vincent PS: a small thought, the idea of one release manager for both java and php is maybe not appropriated in our context...
