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

[TB] Prepare new release of Theme Builder #827

Open
4 tasks done
aaronreed708 opened this issue Apr 16, 2024 · 3 comments
Open
4 tasks done

[TB] Prepare new release of Theme Builder #827

aaronreed708 opened this issue Apr 16, 2024 · 3 comments
Assignees
Labels
project management Administrative activities for open project theme builder app Theme Builder application

Comments

@aaronreed708
Copy link
Contributor

aaronreed708 commented Apr 16, 2024

Problem/Concern

We have recently put in new changes to our documentation and updated our dependencies. We should push out a new version of Theme Builder with these changes so that any new participants are looking at the new changes. At the highest level, this simply means pushing from dev branch to master. But we need to follow our release process (follow, improve #720). Particularly remember to do container scanning and posting results in /securityscanning.

Questions:

  • Current release level of Theme Builder is v1.1.0. What should new version be? v1.2.0?
  • Decide on timeframe
  • Any pending changes worth waiting for?
  • I assume new release of SDK, too? Is it at a good point to push to master?
@aaronreed708 aaronreed708 added project management Administrative activities for open project theme builder app Theme Builder application labels Apr 16, 2024
@aaronreed708 aaronreed708 self-assigned this Apr 16, 2024
@PaulaPaul
Copy link
Contributor

@evangk6 - here are my notes (please feel free to add/correct if needed!)

On today's call we decided the new version would be 1.2.0 (no breaking changes, but more than just updating dependencies)

Expecting @aaronreed708 to create the release, and once Keith's changes are in for the SDK we can release.

Please let @PaulaPaul know and she can help amplify the release through FINOS-

@evangk6
Copy link
Contributor

evangk6 commented Apr 18, 2024

Thanks Paula!

I'll add that specific changes we are waiting on are #501, and the update should therefore in include the SDK as well.

@aaronreed708
Copy link
Contributor Author

We have an issue that needs to be corrected in our Docker images due to chroma-js issue (#983). We also have some dependency updates that need to be propagated to main. I am proposing that we make this change before #501 is ready so that our latest Docker image doesn't remain broken much longer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
project management Administrative activities for open project theme builder app Theme Builder application
Projects
Status: High Priority
Development

No branches or pull requests

3 participants