Skip to content

Adding a section about new releases blog #2795

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Sep 28, 2020
Merged

Adding a section about new releases blog #2795

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
dd79d8b
Adding a section about new releases blog
macruzbar Sep 9, 2020
f5f367e
Update blog/README.md
macruzbar Sep 9, 2020
8d497c7
Update blog/README.md
macruzbar Sep 24, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion blog/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ To submit a blog post, follow the steps below.

#### Suitable content:
- **Original content only**
- Knative new feature releases and project updates
- Knative [new feature releases and project updates](## Communicating new project releases)
- Tutorials and demos [start a blog](https://github.com/knative/docs/pull/2511)
- Use cases
- Content that is specific to a vendor or platform about Knative installation and use
Expand All @@ -44,6 +44,10 @@ To submit a blog post, follow the steps below.
- Content that doesn't interact with Knative APIs or interfaces
- Vendor pitches

## Communicating new project releases
**Scheduled releases:** The Knative project has a release every 6 weeks, and we need your help communicating new changes to our community! If you would like to contribute a blog post to the Knative blog, please consider writing about the latest changes to the project. Ideally, there should be a single blog post for every release version, for example, 0.17; 0.18; 0.19. The title convention should be: *Version [version number] release - [date]*. Release blog contributors should write a summary of the changes and select up to 3 highlights of the current release to write about.
**Big changes to the project.** Big changes to the project require a deep dive blog that describes the new feature in detail and give examples of the new functionality.

## Review Process

After a blog post is submitted as a PR, it is automatically assigned to a reviewer.
Expand Down