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.

Sign up for GitHub

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

Jump to bottom

[REPOSITORY] Prepare release with automatically deliverable artifacts #63

Open
svlad-90 opened this issue Jul 4, 2020 · 0 comments
Open

[REPOSITORY] Prepare release with automatically deliverable artifacts #63

svlad-90 opened this issue Jul 4, 2020 · 0 comments
Assignees
@svlad-90
Labels
enhancement New feature or request good first issue Good for newcomers non functional optimization Issue is related to coverage of the technical debt
Milestone
backlog

Comments

@svlad-90
Copy link
Owner

svlad-90 commented Jul 4, 2020 •
edited
Loading

In order to increase the level of the support of our users, we need to start to prepare releases with automatically deliverable artifacts.

Currently, we need the following builds to be supported:

  • Windows build for msvc-2013 & Qt 5.5.1 for version 2.19 of the dlt-viewer ( to support one of the actual projects )
  • Windows build for msvc-2013 & Qt 5.5.1 for version 2.20 of the dlt-viewer ( to support one of the actual projects )
  • Windows build for msvc-2019 & Qt 5.15.0 for version 2.19 of the dlt-viewer
  • Windows build for msvc-2019 & Qt 5.15.0 for version 2.20 of the dlt-viewer
  • Linux build

For Windows, the artifact should be an archive with dlt-viewer + DLT-Message-Analyzer plugin inside.
For Linux, the artifact should be an archive with dlt-viewer's + DLT-Message-Analyzer's source code inside, ready for being compiled with CMake.

For Linux, build is not actually needed, as only the source code is part of the delivery. Still, the corresponding build should compile the code, in order to prevent the delivery of non-compilable source code.
@svlad-90 svlad-90 added enhancement New feature or request non functional optimization Issue is related to coverage of the technical debt labels Jul 4, 2020
@svlad-90 svlad-90 mentioned this issue Jul 4, 2020
Closed
@svlad-90 svlad-90 added the good first issue Good for newcomers label Aug 5, 2020
@svlad-90 svlad-90 self-assigned this Aug 16, 2020
@svlad-90 svlad-90 modified the milestones: v.1.0.24, backlog Aug 16, 2020
@svlad-90 svlad-90 modified the milestones: backlog, v.1.0.25 Jan 4, 2021
@svlad-90 svlad-90 mentioned this issue Jun 11, 2021
Closed
@svlad-90 svlad-90 modified the milestones: v.1.0.25, v.1.0.27 May 25, 2023
@svlad-90 svlad-90 modified the milestones: v.1.0.27, v.1.0.28 Nov 15, 2023
@svlad-90 svlad-90 modified the milestones: v.1.0.28, backlog Jul 23, 2024
@svlad-90 svlad-90 moved this to To do in DLTMessageAnalyzer Jul 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@svlad-90 svlad-90

Labels
enhancement New feature or request good first issue Good for newcomers non functional optimization Issue is related to coverage of the technical debt
Projects
DLTMessageAnalyzer
Status: To do
Milestone
backlog
Development

No branches or pull requests
1 participant
@svlad-90