On 6/29/14 9:10 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote:
>> >> something that's missing. We are not allowed to use nightly builds as a >> rapid release mechanism. >> > >That is silly. I think we should beat the lawyers at their own game and >just refrain from calling the nightlies "releases" and proceed to make >them >the way early adopters meet FlexJS. > >The release process should be simple and fast. There are discussions on >> other Apache lists on how to make releasing simpler and faster. In >>theory >> it is supposed to encourage more participation as well as potential >> committers and patchers see their work released sooner. >> > >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. Thanks, -Alex
