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

Complete knowledge transfer for new core-plan maintainers #2544

Closed
4 tasks done
gavindidrichsen opened this issue May 4, 2019 · 3 comments
Closed
4 tasks done

Complete knowledge transfer for new core-plan maintainers #2544

gavindidrichsen opened this issue May 4, 2019 · 3 comments
Assignees

Comments

@gavindidrichsen
Copy link
Contributor

gavindidrichsen commented May 4, 2019

Context

Adding this issue as a placeholder for ongoing agenda items to be addressed on weekly knowledge transfer call.

Completed

  • Pair with Scott to do core plan promotion
  • Agreed to delay promotion of core/sed test PR so as not to impact other dependent plans
  • Should we update bats-core according to Stocksy's issue? Yes, the version of bats-core can be updated, but don't add bats-support because this would break best-practice turning this into a composite plan
  • If changes are made to a plan, like adding tests, would we need to up the minor version X.X.??? Generally no. core-plan versions typically link to a 3rd party software at a specific version. Plan and software should be aligned.
@gavindidrichsen gavindidrichsen self-assigned this May 4, 2019
@gavindidrichsen
Copy link
Contributor Author

Hi @james-stocks, @smacfarlane. Adding this issue to hold agenda items for our weekly knowledge transfer calls.

@james-stocks
Copy link

I don't think this is the right medium for tracking agenda items - suggest Slack or Trello instead.

@gavindidrichsen
Copy link
Contributor Author

Closing this and moving to another location

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

2 participants