Skip to content
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.

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

post style to blog style #3

Merged
merged 2 commits into from
Feb 24, 2022

Conversation

stockholmux
Copy link

Signed-off-by: Kyle Davis kyledvs@amazon.com

Description

  • Changes the original forum post style to blog style
  • Resolves typos and rendering problems
  • Changes date of post

By submitting this pull request, I confirm that my contribution is made under the terms of the BSD-3-Clause License.

Signed-off-by: Kyle Davis <kyledvs@amazon.com>
_posts/2022-02-23-roadmap-proposal.md Outdated Show resolved Hide resolved
_posts/2022-02-23-roadmap-proposal.md Outdated Show resolved Hide resolved

3. **The project will follow a "release train" model for minor-version releases, and a "tentpole" model for major-version releases.**
The team wants to produce minor-version releases on a "release-train" schedule: every six weeks a new release comes out, and it includes all the new features that are ready at the time of release. Having a set release schedule makes sure OpenSearch is releasing in a predictable way and prevents a backlog of unreleased changes. In contrast, major-version releases will take place when there is a critical mass of new features that would create incompatibilities, since that’s the only opportunity to release them. These are called "tentpole" features because getting one of these in might hold a release. If any of the tentpole changes runs into serious problems, a decision would need to be made to move the release or wait until the next major release for that change.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That passive voice in the last sentence raises more questions than it answers, I think?

If any of the tentpole changes runs into serious problems, the folks working on it will need to add a comment on their meta tracking issue with an alert. At that point we the folks working on the issue and I can decide whether to cut scope, remove the feature from the release, or move the release date depending on the type and severity of the problem.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll sub in.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"folks" is weird I acknowledge, BTW. So if you have a better word feel free to swap it in (tent pole features can come from anywhere.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Contributors?

_posts/2022-02-23-roadmap-proposal.md Outdated Show resolved Hide resolved
Signed-off-by: Kyle Davis <kyledvs@amazon.com>
@elfisher elfisher merged commit c6bfd05 into elfisher:adds-roadmap-blog Feb 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants