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

improve release notes flow #96

Closed
jamieklassen opened this issue Aug 12, 2019 · 1 comment
Closed

improve release notes flow #96

jamieklassen opened this issue Aug 12, 2019 · 1 comment
Assignees
Milestone

Comments

@jamieklassen
Copy link
Member

jamieklassen commented Aug 12, 2019

  • store release notes in concourse/concourse
  • write release notes in markdown instead of booklit
  • remove any CI pipeline references to concourse/release-notes
  • destroy the concourse/release-notes repo
@jamieklassen jamieklassen added this to the v5.5.0 milestone Aug 12, 2019
jamieklassen pushed a commit that referenced this issue Aug 22, 2019
Fixes #96

Signed-off-by: Denise Yu <dyu@pivotal.io>
Co-authored-by: James Thomson <jthomson@pivotal.io>
@jomsie
Copy link

jomsie commented Aug 22, 2019

Thinking about the new flow re: release notes.

Since the release notes md files are in concourse/release_notes, we were thinking of having a latest.md file in there, and whenever anyone makes a PR to concourse/concourse, they'd also add their release note in there.

Then once it's time to release a new version of concourse, before the shipit job, the releng pair will have to copy latest.md to v{version}.md, clear out latest.md, and then make a PR with those changes.

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

No branches or pull requests

3 participants