IntenseWebs/opentofu
3
0
Fork 0
mirror of https://github.com/opentofu/opentofu.git synced 2025-01-26 16:36:26 -06:00
Code Issues Packages Projects Releases Wiki Activity

Weekly update for the 2023-10-24 (#781)

Browse Source 
Signed-off-by: Jakub Martin <kubam@spacelift.io>
This commit is contained in:
Kuba Martin 2023-10-24 16:06:32 +02:00 committed by GitHub
parent a4018f95cc
commit 45e5056626
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 26 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
WEEKLY_UPDATES.md
View File

@ -1,5 +1,31 @@
# Weekly Updates
## 2023-10-24
Hey!
This week was again spent on discussing and PoC'in stable registry designs, as well as work on the S3 backend.
- Current Status
- There are [two registry RFCs right now](https://github.com/opentofu/opentofu/issues?q=is%3Aopen+is%3Aissue+label%3Arfc+label%3Af-registry), and both will most likely have a PoC by the end of the week.
- [Extensive work is happening](https://github.com/opentofu/opentofu/issues/700) around updating the S3 state backend configuration to be in line with the AWS provider configuration.
- OpenTofu is available on Homebrew Core, so you can just `brew install opentofu` to use it!
- A [bug report](https://github.com/opentofu/opentofu/issues/763) has surfaced an interesting issue when migrating from Terraform to OpenTofu with an existing state file. An initial fix [has already been implemented](https://github.com/opentofu/opentofu/pull/773) and will be further polished and released soon.
- Up next
- The steering committee will pick a registry RFC in the week of 30th Oct - 3rd Nov.
- Intense implementation work will start on the 6th of November.
- This should let us have a stable registry in place around mid-November - mid-December.
- How can I help?
- Since the alpha release is out, right now the best way to help is to take the alpha for a test drive and see if there are any bugs / issues.
- You can also submit and discuss RFCs related to the stable registry.
- Other than that, the best way to help is to create issues, discuss on issues, and spread the word about OpenTofu.
- There are some occasional minor issues which are accepted and open to external contribution, esp. ones outside the release-blocking path. We’re also happy to accept any minor refactors or linter fixes. [Please see the contributing guide for more details](https://github.com/opentofu/opentofu/blob/main/CONTRIBUTING.md).
- We have multiple engineers available full-time in the core team, so we’re generally trying to own any issues that are release blockers - this way we can make sure we get to the release as soon as possible.
- The amount of pending-decision-labeled issues on the repository might be a bit off-putting. The reason for that is that right now we’re prioritizing the alpha and stable release. Only after we have a stable release in place do we aim to start actually accepting enhancement proposals and getting them implemented/merged. Still, we encourage you to open those issues and discuss them!
- Issues and Pull Requests with enhancements or major changes will generally be frozen until we have the first stable release out. We will introduce a milestone to mark them as such more clearly.
Please let us know if you have any feedback on what we could improve, either with these updates or more generally - this very document was a result of such feedback! We're available on Slack, via GitHub issues, or even in the pull request updating this file.
## 2023-10-17
Hello there!