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.
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.
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 mharrison@chef.io 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.
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.
On Thu, Jan 22, 2015 at 1:28 PM, Mark Harrison mharrison@chef.io 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 mharrison@chef.io 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.
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.
On Thu, Jan 22, 2015 at 1:28 PM, Mark Harrison mharrison@chef.io 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 mharrison@chef.io 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.
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.
The migration into chef-cookbooks is going to work a little differently.
Instead of renaming the organization, we are going to be be moving
cookbooks one by one, as they go through heavy duty QA and testing
procedures. For now, the opscode-cookbooks organization will remain
until all cookbooks have been migrated or adopted.
Thanks,
Mark
On Fri, Jan 30, 2015 at 4:49 AM, Torben Knerr mail@tknerr.de wrote:
On Thu, Jan 22, 2015 at 1:28 PM, Mark Harrison mharrison@chef.io 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 mharrison@chef.io 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.
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.
On Fri, Jan 30, 2015 at 4:21 PM, Mark Harrison mharrison@chef.io wrote:
Hi Torben,
The migration into chef-cookbooks is going to work a little differently.
Instead of renaming the organization, we are going to be be moving
cookbooks one by one, as they go through heavy duty QA and testing
procedures. For now, the opscode-cookbooks organization will remain
until all cookbooks have been migrated or adopted.
Thanks,
Mark
On Fri, Jan 30, 2015 at 4:49 AM, Torben Knerr mail@tknerr.de wrote:
On Thu, Jan 22, 2015 at 1:28 PM, Mark Harrison mharrison@chef.io 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 mharrison@chef.io 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.
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.