What about jclouds-labs-openstack?

That needs to be part of the release process too.

Thanks,
Everett

On Aug 2, 2013, at 8:38 AM, Andrew Phillips wrote:

> As per the discussion, [lease consider the following repos as "frozen":
> 
> * incubating-jclouds.git
> 
> frozen at 
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds.git;a=commit;h=8688d8e0c3803295c52e912e5a6d543c841fbd55
> 
> * incubating-jclouds-labs.git
> 
> frozen at 
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-labs.git;a=commit;h=3300d3acf870677accbb65d07298c2e33037b943
> 
> * incubating-jclouds-chef.git
> 
> frozen at 
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-chef.git;a=commit;h=44fba95ba5df14c392f5277b36716b66f9a5434e
> 
> * incubating-jclouds-karaf.git
> 
> frozen at 
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-karaf.git;a=shortlog;h=refs/heads/1.6.x
> 
> * incubating-jclouds-cli.git
> 
> frozen at 
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-cli.git;a=commit;h=a08af620e282628528bdc0f34c1ecdb36159623f
> 
> We'll get started on the release procedure for 1.6.2-incubating now. Since 
> we're not voting yet, we can still include fixed for any urgent regressions 
> we uncover. I propose that we don't add any new features to 1.6.2-incubating 
> any more, though.
> 
> Here goes!
> 
> ap

Reply via email to