> > >OK, that's nice and all, but let's get into specifics. What do you suggest > >we do to simplify and speed up the release process of the separate > >projects? > The approval scripts attempt to get you to vote with less hassle. There > could be more improvements in the scripts to show diffs in LICENSE and > NOTICE so you know if additional scrutiny is needed. I'm definitely open > to more ideas here. For me, when I see a vote thread come out I think "oh > crap, now I have to take a bunch of time to review this thing" and we > wan't folks to say "oh cool, new stuff is coming out, let me help by > voting (without the vote losing its value). I just found out the > installer.xml will run to completion in a built source package (I haven't > proven it works in an IDE yet) but that could be added to the script as > well so after you prove the RC builds you can turn it into an IDE SDK and > test it in your IDE just by answering 'y' to one of the prompts in the > approval script. > > And I'm going to look into ant scripts that run all of the git tagging and > svn committing required to push an RC. >
Also, I suggest that we keep to the actual voting rules: when 72 hrs pass, there are 3 or more +1 votes and more +1 votes than -1 votes, a release should be released. By this agreed upon standard (see the wiki), I think at least some of the recent RCs are actually releases... EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
