-
Notifications
You must be signed in to change notification settings - Fork 2
Added sprint retrospective notes for retro 2025-08-28 #92
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
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
71 changes: 71 additions & 0 deletions
71
doc/processes/retrospective-notes/Retrospective-Notes-2025.08.28.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,71 @@ | ||
# 2025-08-28 | ||
|
||
## Sprint 2025-08-28 Retrospective (2025-10-01) | ||
|
||
| Chair | Timekeeper | Note Taker | | ||
|-------|------------|------------| | ||
| TW | KB | IG | | ||
|
||
## Items from previous Retrospective | ||
### NDW1926 Linux build? | ||
- *ACTION*: FA To check with CMS how to adopt Windows 10 LTS for build server. | ||
|
||
### ISIS Shares (\\isis\shares) organisation - have not got around to it yet. | ||
- Carry over to next retro. | ||
|
||
## Items from this retrospective: | ||
### Review of First Line Support | ||
- Discussion were had around the adoption of the first line support procedure. | ||
- GR identified that there was a problem where some issues were not picked up and missed from being actioned. | ||
- GR suggested a formal handover at the end of a week, perhaps write up a Friday summary of the week. | ||
- GR mentioned that Top Desk is the corporate platform and maybe we should look at using it. | ||
- FA Mentioned `Jira`, but it's not free and we would need to look at licensing. | ||
- FA suggests adopting a system where we can enter issues and close them out. | ||
- *ACTION*: FA to consider options in conversation with team members. | ||
|
||
### Developer Manual - protection of master branch | ||
- There was a bit of a debate in comparison between the ease of updating the manual versus the | ||
ideology that documentation should be at the same quality as code. | ||
- It was decided that instead of committing directly to master, we should have a trial period of | ||
creating PRs and flash-reviews. This policy should be reviewed at a later date to consider its efficacy. | ||
|
||
### Documentation on wiki instrument-information--hotfixes | ||
- JH raised the question as to whether we need to our hotfix/deploy process and suggests that we | ||
should either keep the hotfixes page up to date or remove it. | ||
- FA suggests creating a flash review or ticket. | ||
- Remove the Hotfix column. | ||
- Deploy scripts to not prompt to add text to the hotfix column. | ||
|
||
### Wiki instrument information pages are significantly out of date | ||
- GR asked whether we should make an effort to improve them, as having a page is useful for instrument support? | ||
- TW posed the question as to whether we should use the existing pages as a starting point or bin them and start again? | ||
- *ACTION*: TW to place a warning at the top of every page stating that the current information is | ||
historical content and may not be up to date. | ||
|
||
### Disc space | ||
- TW stated that small discs on various machines has caused repeated issues. | ||
- *ACTION*: GR to set up a group meeting with CMS to discuss. | ||
|
||
### Weird permissions on stage-deleted | ||
- Could we modify permissions of the stage-deleted folder or perhaps don't use it? | ||
- Issue bumped until CMS is available to discuss. | ||
|
||
### Timings of deploys | ||
- GR commented that deployments being scheduled only a couple of weeks before cycle and during Summer holidays | ||
can be problematic, the Summer being of particular issue. | ||
- We should attempt to deploy a week earlier and deliver demos earlier. | ||
|
||
### Deploy script refinement | ||
- TW pointed out that occasionally a manual step in the deployment process does not get done, but | ||
there is no check that it actually has been done. | ||
- The Road-map should incorporate procedures to address this. | ||
|
||
### Renaming of 'server-common' | ||
- JH suggested that we should rename 'server-common' to 'ibex-ca-helpers'. | ||
- FA suggested 'ibex-epics-helpers' | ||
- *ACTION*: JH to find some suitable names | ||
|
||
### Galil-old branch | ||
- FA suggested that a repo check on galil-old would be a good idea. | ||
- *ACTION*: FA to create a ticket to create a repo check on galil-old. | ||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Filename should follow the same convention as all the others so that it sorts properly in the rendered wiki:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!