+1 I think storing this release tooling in SVN is totally fine for now. I suppose an alternative could be a jclouds scripts repo or something similar in git, but that is a bit more work for infra and might be overkill. SVN seems to be a good solution for now.
Thanks for the work on this Ignasi! Thanks, Chris -- Chris Custine From: Andrew Phillips <aphill...@qrmedia.com> Reply: dev@jclouds.apache.org <dev@jclouds.apache.org>> Date: March 26, 2015 at 7:54:45 AM To: dev@jclouds.apache.org <dev@jclouds.apache.org>> Subject: Re: COMMERCIAL:Automated releases > Personally, I see more benefits and more convenient to have the > release scripts in SVN. Based on what you explained, Ignasi, I tend to agree - especially to break the "circular dep" between using the release script to generate the release and having to tweak it. SVN seems fine for me - I'd then just say that we should include those things that are already in the "scripts" directory in jclouds/jclouds there too. Regards ap
