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

Implement Automated Release and Multi-Architecture Compilation Strategy for the Core Repository #261

Closed
cubxxw opened this issue Aug 18, 2023 — with Slack · 0 comments · Fixed by #262
Closed
Assignees
Labels
enhancement New feature or request feature Categorizes issue or PR as related to a new feature. release/v3.0 Issues and pull requests related to version 3.0 of the release. This is the current version.
Milestone

Comments

Copy link
Contributor

cubxxw commented Aug 18, 2023

Description:

In order to address the evolving needs of our user base and streamline our development and deployment processes, it's imperative that we implement an automated release and multi-architecture compilation strategy for the Core Repository. This enhancement will not only reduce manual intervention but also ensure compatibility across diverse hardware architectures.

Objectives:

  1. Automated Release

    : Automate the process of packaging and releasing new versions of the software in the Core Repository. This should include:

    • Version bumping.
    • Change-log generation.
    • Notification to stakeholders.
  2. Multi-Architecture Compilation:

    • Ensure that our software is compilable and runs efficiently on multiple hardware architectures.
    • Implement CI/CD checks for common architectures like x86_64, ARM64, etc.
    • Provide documentation for supported architectures and potential pitfalls or optimizations for each.

Steps:

  1. Evaluate and select appropriate CI/CD tools that support multi-architecture builds (e.g., Jenkins, GitHub Actions, Travis CI).
  2. Implement automated versioning and release workflows.
  3. Add compilation steps for different architectures in the CI/CD pipeline.
  4. Test builds on actual hardware or emulated environments to ensure proper functionality.
  5. Document the new workflows and provide guidelines for contributors and maintainers.

Additional Information:

  • Any pre-existing tools or scripts that could aid in this transition should be mentioned.
  • We might need to consider potential licensing or costs associated with some CI/CD tools.
@cubxxw cubxxw added enhancement New feature or request feature Categorizes issue or PR as related to a new feature. release/v3.0 Issues and pull requests related to version 3.0 of the release. This is the current version. labels Aug 18, 2023 — with Slack
@cubxxw cubxxw added this to the v3.1 milestone Aug 18, 2023 — with Slack
@cubxxw cubxxw self-assigned this Aug 18, 2023
@cubxxw cubxxw mentioned this issue Aug 18, 2023
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request feature Categorizes issue or PR as related to a new feature. release/v3.0 Issues and pull requests related to version 3.0 of the release. This is the current version.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant