Move to beta

[fnattino]

The lesson has been taught few times now, so it should qualify for the beta stage

[github-actions]

Thank you!

Thank you for your pull request 😃

🤖 This automated message can help you check the rendered files in your submission for clarity. If you have any questions, please feel free to open an issue in {sandpaper}.

If you have files that automatically render output (e.g. R Markdown), then you should check for the following:

• 🎯 correct output
• 🖼️ correct figures
• ❓ new warnings
• ‼️ new errors

Rendered Changes

🔍 Inspect the changes: https://github.com/carpentries-incubator/geospatial-python/compare/md-outputs..md-outputs-PR-163

The following changes were observed in the rendered markdown documents:

 config.yaml | 2 +-
 md5sum.txt  | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

What does this mean?

If you have source files that require output and figures to be generated (e.g. R Markdown), then it is important to make sure the generated figures and output are reproducible.

This output provides a way for you to inspect the output in a diff-friendly manner so that it's easy to see the changes that occur due to new software versions or randomisation.

⏱️ Updated at 2023-09-28 12:10:01 +0000

[fnattino]

@rbavery @rogerkuou @mkuzak

[rbavery]

@tobyhodges Is this good to merge to change the lifecycle stage to beta?

This was taught at the Netherlands ESciences center a few times, NASA DEVELOP at JPL, and twice at the IGARSS 2023 conference in Pasadena. Instructors that have covered this material include @rbavery @rogerkuou @mkuzak @fnattino and @chuckwondo

[rbavery]

@fnattino I've opened an issue here, I think it needs to go through a formal review process: carpentries-lab/reviews#27

[rbavery]

Toby said it's all good to merge, merging.