- From: Mark Harrison <
>
- To:
- Subject: [chef] Re: Chef github organization rename
- Date: Thu, 22 Jan 2015 14:49:37 -0500
Hi everyone,
The organization rename is now complete. You can now access chef's
public code by going to
https://github.com/chef/chef (and similar for
other repository names) in addition to the old names.
Regards,
Mark
On Thu, Jan 22, 2015 at 1:28 PM, Mark Harrison
<
>
wrote:
>
Hi all,
>
>
This email is just a reminder that the opscode github organization
>
rename will be happening today in approximately 1 hour (about 30
>
minutes later than originally planned). I'll be sending out another
>
post to the mailing list once the rename is complete.
>
>
Thanks,
>
>
Mark
>
>
On Thu, Jan 15, 2015 at 4:12 PM, Mark Harrison
>
<
>
>
wrote:
>
> Ohai Chefs!
>
>
>
> It’s been a long time coming, but we are finally renaming the opscode
>
> github organizations to ‘chef’. This will be happening on Thursday
>
> January 22 2015 at approximately 11:00 PST/19:00 UTC.
>
>
>
> All repositories will continue to be accessible using their old names,
>
> so those of you with existing checkouts have no need to worry.
>
> However, after that date you will start to see references to
>
> repositories being available from their new names.
>
>
>
> To summarize:
>
>
>
> https://github.com/opscode/repositoryname will become
>
> https://github.com/chef/repositoryname
>
>
>
> and similar changes will be made for accessing repositories via ssh
>
> and the git protocol.
>
>
>
> The migration into chef-cookbooks will work a little differently.
>
> Instead of renaming the org and being done with it, we will be moving
>
> cookbooks one by one, as they go through heavy duty QA and testing
>
> procedures. The opscode-cookbooks organization will remain until all
>
> cookbooks have been migrated or adopted.
>
>
>
> Thanks,
>
>
>
> Mark Harrison
>
> Systems Administrator, Chef
Archive powered by MHonArc 2.6.16.