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.

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

Jump to bottom

HPCC-31384 Add release cadence to README.md #18368

Merged
merged 1 commit into from
Jul 16, 2024
Merged

HPCC-31384 Add release cadence to README.md #18368

merged 1 commit into from
Jul 16, 2024

Conversation

GordonSmith
Copy link
Member

@GordonSmith GordonSmith commented Mar 1, 2024 •
edited
Loading

Type of change:

  • This change is a bug fix (non-breaking change which fixes an issue).
  • This change is a new feature (non-breaking change which adds functionality).
  • This change improves the code (refactor or other change that does not change the functionality)
  • This change fixes warnings (the fix does not alter the functionality or the generated code)
  • This change is a breaking change (fix or feature that will cause existing behavior to change).
  • This change alters the query API (existing queries will have to be recompiled)

Checklist:

  • My code follows the code style of this project.
    • My code does not create any new warnings from compiler, build system, or lint.
  • The commit message is properly formatted and free of typos.
    • The commit message title makes sense in a changelog, by itself.
    • The commit is signed.
  • My change requires a change to the documentation.
    • I have updated the documentation accordingly, or...
    • I have created a JIRA ticket to update the documentation.
    • Any new interfaces or exported functions are appropriately commented.
  • I have read the CONTRIBUTORS document.
  • The change has been fully tested:
    • I have added tests to cover my changes.
    • All new and existing tests passed.
    • I have checked that this change does not introduce memory leaks.
    • I have used Valgrind or similar tools to check for potential issues.
  • I have given due consideration to all of the following potential concerns:
    • Scalability
    • Performance
    • Security
    • Thread-safety
    • Cloud-compatibility
    • Premature optimization
    • Existing deployed queries will not be broken
    • This change fixes the problem, not just the symptom
    • The target branch of this pull request is appropriate for such a change.
  • There are no similar instances of the same problem that should be addressed
    • I have addressed them here
    • I have raised JIRA issues to address them separately
  • This is a user interface / front-end modification
    • I have tested my changes in multiple modern browsers
    • The component(s) render as expected

Smoketest:

  • Send notifications about my Pull Request position in Smoketest queue.
  • Test my draft Pull Request.

Testing:

@GordonSmith GordonSmith requested a review from ghalliday March 1, 2024 12:57
@GordonSmith
Copy link
Member Author

@ghalliday you preview how it renders here:
image

@github-actions GitHub Actions
Copy link

github-actions bot commented Mar 1, 2024

https://track.hpccsystems.com/browse/HPCC-31384
Jira updated

ghalliday
ghalliday reviewed Mar 6, 2024
View reviewed changes
Copy link
Member

@ghalliday ghalliday left a comment

Choose a reason for hiding this comment

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

Looks good. Some suggested changes to the dates.

README.md Outdated
Active: done, 2022-10-01, 1y
Security: active, 6M
section v9.2.x
Active: active, 2023-04-01, 1y
Copy link
Member

Choose a reason for hiding this comment

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

2023-07-01, 6M

README.md Outdated
Active: done, 2022-04-01, 1y
Security: done, 6M
section v9.0.x
Active: done, 2022-10-01, 1y
Copy link
Member

Choose a reason for hiding this comment

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

2023-04-01, 9M

README.md Outdated
tickInterval 3month
dateFormat YYYY-MM-DD
section v8.12.x
Active: done, 2022-04-01, 1y
Copy link
Member

Choose a reason for hiding this comment

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

2023-02-07, 6M

README.md Outdated
dateFormat YYYY-MM-DD
section v8.12.x
Active: done, 2022-04-01, 1y
Security: done, 6M
Copy link
Member

Choose a reason for hiding this comment

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

9M

README.md Outdated
Active: active, 2023-04-01, 1y
Security: 6M
section v9.4.x
Active: active, 2023-10-01, 1y
Copy link
Member

Choose a reason for hiding this comment

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

, 9M

@GordonSmith GordonSmith force-pushed the HPCC-31384-RELEASE_CADENCE branch from abbbf56 to b7af725 Compare March 6, 2024 13:18
@GordonSmith GordonSmith requested a review from ghalliday March 6, 2024 13:18
ghalliday
ghalliday reviewed Mar 7, 2024
View reviewed changes
README.md Outdated
Active: active, 2023-10-01, 9M
Security: 6M
section v9.6.x
Active: 2024-04-01, 1y
Copy link
Member

Choose a reason for hiding this comment

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

, 6M and also line 43. Standard is really 6M active, 6M security, but it has changed a bit around the 9.4.x release.

ghalliday
ghalliday reviewed Mar 7, 2024
View reviewed changes
Copy link
Member

@ghalliday ghalliday left a comment

Choose a reason for hiding this comment

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

@GordonSmith a couple of final comments

README.md Outdated
@@ -9,6 +9,41 @@ HPCC Systems offers an enterprise ready, open source supercomputing platform to
* [Installation and Running](https://hpccsystems.com/training/documentation/installation-and-administration)
* [Developer Documentation](https://hpcc-systems.github.io/HPCC-Platform/)

# Release + Support Policy

In general, a new version of the HPCC Platform is released every 6 months. These releases can be either Major (with breaking changes) or Minor (with new features). Maintenance and security releases (point releases) are typically made weekly, and may occasionally include technical previews.
Copy link
Member

Choose a reason for hiding this comment

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

Every 3 months

@GordonSmith GordonSmith force-pushed the HPCC-31384-RELEASE_CADENCE branch from b7af725 to 3b9faa0 Compare March 14, 2024 11:46
@GordonSmith GordonSmith requested a review from ghalliday March 14, 2024 11:46
@GordonSmith
Copy link
Member Author

Updated and squashed.

ghalliday
ghalliday requested changes Mar 14, 2024
View reviewed changes
Copy link
Member

@ghalliday ghalliday left a comment

Choose a reason for hiding this comment

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

Active is still too long for 9.6 and 10.0.0. Also 10.0.0 is more likely to be 9.8.

@GordonSmith GordonSmith requested a review from cloLN July 2, 2024 15:39
@GordonSmith GordonSmith force-pushed the HPCC-31384-RELEASE_CADENCE branch from 3b9faa0 to 4fb628a Compare July 4, 2024 05:05
@GordonSmith
Copy link
Member Author

GordonSmith commented Jul 4, 2024 •
edited
Loading

@ghalliday, @cloLN - updated to include 9.8.x and 9.10.x

image

@GordonSmith GordonSmith requested a review from ghalliday July 4, 2024 05:07
@cloLN
Copy link
Contributor

cloLN commented Jul 8, 2024

Looks good. thanks.

cloLN
cloLN approved these changes Jul 9, 2024
View reviewed changes
Copy link
Contributor

@cloLN cloLN left a comment

Choose a reason for hiding this comment

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

Changes look good.

@ghalliday ghalliday merged commit 7ff8447 into hpcc-systems:master Jul 16, 2024
28 of 52 checks passed
@GordonSmith GordonSmith deleted the HPCC-31384-RELEASE_CADENCE branch July 16, 2024 08:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@cloLN cloLN cloLN approved these changes

@ghalliday ghalliday ghalliday approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@GordonSmith @cloLN @ghalliday