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

[RELEASE] 0.6.0 #356

Merged
merged 374 commits into from
Oct 9, 2024
Merged

[RELEASE] 0.6.0 #356

merged 374 commits into from
Oct 9, 2024

Conversation

aziolek
Copy link
Member

@aziolek aziolek commented Jul 23, 2024

Description

Definition of Done

  1. Acceptance criteria are met.
  2. PR is manually tested before the merge by developer(s). - [ ] Happy path is manually checked.
  3. PR is manually tested by QA when their assistance is required (1).
  • Octant Areas & Test Cases are checked for impact and updated if required (2).
  1. Unit tests are added unless there is a reason to omit them.
  2. Automated tests are added when required.
  3. The code is merged.
  4. Tech documentation is added / updated, reviewed and approved (including mandatory approval by a code owner, should such exist for changed files).
    • BE: Swagger documentation is updated.
  5. When required by QA: - [ ] Deployed to the relevant environment. - [ ] Passed system tests.

(1) Developer(s) in coordination with QA decide whether it's required. For small tickets introducing small changes QA assistance is most probably not required.

(2) Octant Areas & Test
Cases
.

@aziolek aziolek self-assigned this Jul 23, 2024
@aziolek aziolek added the request-approval Request approval from the Housekeeper label Jul 26, 2024
@housekeeper-bot housekeeper-bot removed the request-approval Request approval from the Housekeeper label Jul 26, 2024
Copy link
Contributor

@housekeeper-bot housekeeper-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

E2E job #10113197831 passed 🎉

@housekeeper-bot housekeeper-bot temporarily deployed to uat August 9, 2024 06:51 Destroyed
@housekeeper-bot housekeeper-bot temporarily deployed to uat August 21, 2024 12:02 Destroyed
@housekeeper-bot housekeeper-bot temporarily deployed to uat August 21, 2024 12:18 Destroyed
@housekeeper-bot housekeeper-bot temporarily deployed to uat August 21, 2024 12:39 Destroyed
@housekeeper-bot housekeeper-bot temporarily deployed to uat August 21, 2024 13:12 Destroyed
@housekeeper-bot housekeeper-bot temporarily deployed to uat August 21, 2024 13:42 Destroyed
@housekeeper-bot housekeeper-bot temporarily deployed to uat August 21, 2024 13:59 Destroyed
@housekeeper-bot housekeeper-bot temporarily deployed to uat August 21, 2024 14:57 Destroyed
@housekeeper-bot housekeeper-bot temporarily deployed to uat August 22, 2024 09:18 Destroyed
@housekeeper-bot housekeeper-bot temporarily deployed to uat August 23, 2024 11:50 Destroyed
@housekeeper-bot housekeeper-bot temporarily deployed to uat August 25, 2024 21:24 Destroyed
@housekeeper-bot housekeeper-bot temporarily deployed to uat August 28, 2024 08:55 Destroyed
@housekeeper-bot housekeeper-bot temporarily deployed to uat August 28, 2024 09:02 Destroyed
@housekeeper-bot housekeeper-bot temporarily deployed to uat August 28, 2024 12:57 Destroyed
@housekeeper-bot housekeeper-bot temporarily deployed to uat August 29, 2024 14:03 Destroyed
@housekeeper-bot housekeeper-bot temporarily deployed to uat August 29, 2024 18:24 Destroyed
@housekeeper-bot housekeeper-bot temporarily deployed to uat August 29, 2024 19:07 Destroyed
@housekeeper-bot housekeeper-bot temporarily deployed to uat September 4, 2024 08:49 Destroyed
aziolek and others added 7 commits September 13, 2024 13:07
## Description
Check after [PR-406](#406)

## Definition of Done

1. [ ] Acceptance criteria are met.
2. [ ] PR is manually tested before the merge by developer(s).
    - [ ] Happy path is manually checked.
3. [ ] PR is manually tested by QA when their assistance is required
(1).
- [ ] Octant Areas & Test Cases are checked for impact and updated if
required (2).
4. [ ] Unit tests are added unless there is a reason to omit them.
5. [ ] Automated tests are added when required.
6. [ ] The code is merged.
7. [ ] Tech documentation is added / updated, reviewed and approved
(including mandatory approval by a code owner, should such exist for
changed files).
    - [ ] BE: Swagger documentation is updated.
8. [ ] When required by QA:
    - [ ] Deployed to the relevant environment.
    - [ ] Passed system tests.

---

(1) Developer(s) in coordination with QA decide whether it's required.
For small tickets introducing small changes QA assistance is most
probably not required.

(2) [Octant Areas & Test
Cases](https://docs.google.com/spreadsheets/d/1cRe6dxuKJV3a4ZskAwWEPvrFkQm6rEfyUCYwLTYw_Cc).
aziolek and others added 15 commits October 8, 2024 10:34
## Description

## Definition of Done

1. [ ] If required, the desciption of your change is added to the [QA
changelog](https://www.notion.so/octantapp/Changelog-for-the-QA-d96fa3b411cf488bb1d8d9a598d88281)
2. [ ] Acceptance criteria are met.
3. [ ] PR is manually tested before the merge by developer(s).
    - [ ] Happy path is manually checked.
4. [ ] PR is manually tested by QA when their assistance is required
(1).
- [ ] Octant Areas & Test Cases are checked for impact and updated if
required (2).
5. [ ] Unit tests are added unless there is a reason to omit them.
6. [ ] Automated tests are added when required.
7. [ ] The code is merged.
8. [ ] Tech documentation is added / updated, reviewed and approved
(including mandatory approval by a code owner, should such exist for
changed files).
    - [ ] BE: Swagger documentation is updated.
9. [ ] When required by QA:
    - [ ] Deployed to the relevant environment.
    - [ ] Passed system tests.

---

(1) Developer(s) in coordination with QA decide whether it's required.
For small tickets introducing small changes QA assistance is most
probably not required.

(2) [Octant Areas & Test
Cases](https://docs.google.com/spreadsheets/d/1cRe6dxuKJV3a4ZskAwWEPvrFkQm6rEfyUCYwLTYw_Cc).
## Description

## Definition of Done

1. [ ] If required, the desciption of your change is added to the [QA
changelog](https://www.notion.so/octantapp/Changelog-for-the-QA-d96fa3b411cf488bb1d8d9a598d88281)
2. [ ] Acceptance criteria are met.
3. [ ] PR is manually tested before the merge by developer(s).
    - [ ] Happy path is manually checked.
4. [ ] PR is manually tested by QA when their assistance is required
(1).
- [ ] Octant Areas & Test Cases are checked for impact and updated if
required (2).
5. [ ] Unit tests are added unless there is a reason to omit them.
6. [ ] Automated tests are added when required.
7. [ ] The code is merged.
8. [ ] Tech documentation is added / updated, reviewed and approved
(including mandatory approval by a code owner, should such exist for
changed files).
    - [ ] BE: Swagger documentation is updated.
9. [ ] When required by QA:
    - [ ] Deployed to the relevant environment.
    - [ ] Passed system tests.

---

(1) Developer(s) in coordination with QA decide whether it's required.
For small tickets introducing small changes QA assistance is most
probably not required.

(2) [Octant Areas & Test
Cases](https://docs.google.com/spreadsheets/d/1cRe6dxuKJV3a4ZskAwWEPvrFkQm6rEfyUCYwLTYw_Cc).
## Description

## Definition of Done

1. [ ] If required, the desciption of your change is added to the [QA
changelog](https://www.notion.so/octantapp/Changelog-for-the-QA-d96fa3b411cf488bb1d8d9a598d88281)
2. [ ] Acceptance criteria are met.
3. [ ] PR is manually tested before the merge by developer(s).
    - [ ] Happy path is manually checked.
4. [ ] PR is manually tested by QA when their assistance is required
(1).
- [ ] Octant Areas & Test Cases are checked for impact and updated if
required (2).
5. [ ] Unit tests are added unless there is a reason to omit them.
6. [ ] Automated tests are added when required.
7. [ ] The code is merged.
8. [ ] Tech documentation is added / updated, reviewed and approved
(including mandatory approval by a code owner, should such exist for
changed files).
    - [ ] BE: Swagger documentation is updated.
9. [ ] When required by QA:
    - [ ] Deployed to the relevant environment.
    - [ ] Passed system tests.

---

(1) Developer(s) in coordination with QA decide whether it's required.
For small tickets introducing small changes QA assistance is most
probably not required.

(2) [Octant Areas & Test
Cases](https://docs.google.com/spreadsheets/d/1cRe6dxuKJV3a4ZskAwWEPvrFkQm6rEfyUCYwLTYw_Cc).
@aziolek aziolek added the request-approval Request approval from the Housekeeper label Oct 9, 2024
Copy link
Contributor

@MateuszStoleckiGLM MateuszStoleckiGLM left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@housekeeper-bot housekeeper-bot removed the request-approval Request approval from the Housekeeper label Oct 9, 2024
Copy link
Contributor

@housekeeper-bot housekeeper-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

E2E job #11252984896 passed 🎉

@aziolek aziolek merged commit 2f012b6 into master Oct 9, 2024
46 checks passed
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

Successfully merging this pull request may close these issues.

8 participants