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

Add pull request template #234

Merged
merged 1 commit into from
Sep 13, 2022
Merged

Conversation

hovaesco
Copy link
Member

Almost 1:1 copy from Trino repository. It will help maintain release notes in the same way as in Trino project.

@cla-bot cla-bot bot added the cla-signed label Sep 12, 2022
@hovaesco hovaesco mentioned this pull request Sep 12, 2022
@hashhar hashhar requested a review from colebow September 12, 2022 12:35
@hashhar
Copy link
Member

hashhar commented Sep 12, 2022

@colebow PTAL as well.

( ) Release notes are required, with the following suggested text:

```markdown
# Section
Copy link
Member

Choose a reason for hiding this comment

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

This might not be needed in the python client since the release notes are probably just one list of items without sections/headers.

Copy link
Member

Choose a reason for hiding this comment

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

SQLAlchemy, DB-API, General improvements? But yes - it feels overkill for now. We can add it back if needed.

Copy link
Member Author

Choose a reason for hiding this comment

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

Should I remove a whole markdown section then?

Copy link
Member

Choose a reason for hiding this comment

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

I think Manfred just means the # Section header. The markdown template is useful to have.

Copy link
Member Author

Choose a reason for hiding this comment

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

Done

@mosabua
Copy link
Member

mosabua commented Sep 13, 2022

Should we also institute the same process of getting release notes assembled .. maybe even separate file .. or easier.. just an update to the changelog file that was proposed in #221

@hashhar
Copy link
Member

hashhar commented Sep 13, 2022

Should we also institute the same process of getting release notes assembled .. maybe even separate file .. or easier.. just an update to the changelog file that was proposed in #221

We can keep updating the proposed changelog in #221 for every release.

@hovaesco hovaesco force-pushed the hovaesco/pr-template branch from 1e48201 to 8daa427 Compare September 13, 2022 08:10
@hashhar hashhar merged commit c008d9b into trinodb:master Sep 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

3 participants