Open Backlog - Sprint 12 Planning [7.8.x EOL] #7358
A big thanks for participating in the 7.8.x EOL (End of Life) discussion (#7294 & forums) and sharing your thoughts and challenges you face in taking that step from 7.8.x and adopting one of the later versions.
We reviewed the points you all made and broke them down into actionable tasks – though some are too far reaching and will have to be recorded as suggestions for the future. But thankfully much of a feedback we feel can be allocated either within the core team or by community members if able.
In order to help achieve some of the points raised we are designating Dillon & Cameron from the core team for the duration remaining until 7.8.x End of Life has been reached – a couple of sprints from now till end of June.
We also want to introduce a concept we have been mulling about for a while which is to introduce a more direct way to highlight issues into upcoming sprints by setting up pre-sprint backlog.
If you are aware of how Agile works then this is VERY loosely based on this methodology. So simply, prior to an upcoming period of a development cycle, we’ll open up a time limited issue labelled as ‘discussion’ that will ask the community to reference certain existing Github issues that they would like to nominate to be included in the two week sprint (if possible).
The goal we want to achieve here is to have an easier and clearer way to identify publicly the communities’ priorities and how do these issues affect users’ day to day lives.
Though we do need to set the expectations that time is limited to 2 week sprints so if an issue isn’t completed in that sprint it can be re-nominated for the next sprint.
We also encourage ownership of these bugs and their bug fixes (like above). We’ll identify what issues can we tackle and others we suggest community members can address in order to get them into that release.
We are adding new milestone EOL to include issues that we can confirm need to be addressed before the 7.8.x end of life
We are also added new labels “Help Wanted” and “Good First Issue” to help on boarding.
So the mains concepts that people raised that they would like to be seen addressed in 7.10.x+ in order to upgrade are mostly about; Emails; Theme and Misc (things that are singular).
Please see the latest post of the assessment and initial allocation of these issues (see comment below).
We’ve initially identified some that the core team can tackle and have already estimated the effort involved. Anything marked as just Community we offer this up for the Help Wanted label and the items that are Core/Community are those that can be picked up by either! P.S I couldn’t find all Github issues so just comment on which issue links up with an item above.
What we propose then is that in the comments identify bugs, by linking them, that fall under the above themes that you would like to nominate for the upcoming sprint. Feel free to add your suggestions why and even severity of how it impacts your work.
I look forward to seeing how this process will be refined
In no special order, and definitely not a complete list, these are some people who have made past contributions or participated in the Pull Request Party. We'd love to hear from you on the discussion linked above.
@mcarpenterjr Yeah that would be much appreciated. Not all will have a single issue, (for example the email bugs) but if we can try and bring these together then we can physically assign them out and obviously when PRs are created they reference something tangible.
So like, if you feel like ref issues that already exists then please do so and we will pre-assess if they are achieving in the sprint. e.g
This is a great initiative!
We have opened some issues and PR that, in our particularly case, will help us a lot in order to develop solutions over 7.10.x. In some of them, we worked a lot.
We wrote these solutions to satisfy our clients needs, and we would love to see these in 7.10.x. Anyway I am not sure these issues/PR can match with the main idea of this backlog.
Some of them were abandoned, and now need more work.
I give it here what i found...
#7071 (Reply to or Reply to All adding attachment from original email. This should do only Forward function)
this issue move the security management of SuiteCRM on new level.. but in't in sprint
referenced this issue
Jun 11, 2019
Custom icons break when upgrading to 7.10: #5440
I can open a new issue with more info if we want, since that one isn't very detailed. Essentially, when #5273 was merged, the old style of icons was removed in favor of SVG icons. Unfortunately, there was no mention of how to customize the icon font (mostly I'm interested in adding new icons), so I'm not sure what the upgrade path here is supposed to be.
I guess this is related to the better theme documentation?
And of course my pet project of improving the test suite :) #7344
Thanks again for your feedback and referencing the Github issues to help us identify what you feel are your priorities and the issues that are affecting yours & the community's’ daily lives using SuiteCRM.
If you haven’t seen already I had updated the first post with these Github issues that anyone who commented had identified (if I have missed any prior to this post then just holler - check that post history for my revision changes).
Ideally this would’ve been planned and executed prior to the sprint (we are slightly behind to get back with the below) but that is something we can pre-empt in the coming weeks. So, during our sprint planning we reviewed each one and assessed them based on the following criteria: whether the issue is actually a suggestion; whether the issue is code or documentation; whether the issue would be a breaking change; whether the issue could be tackled by either core or community members; & whether the issue could be tackled within a single sprint.
We then allocated each item into a sprint (12, 13) as a very simple baseline on what could be tackled first whilst trying to provide a reasonable distribution of tasks across the sprints for both core team & community. So I do stress this is flexible, if anyone wants to tackle anything that has “Help Wanted” on the issue within a sprint please don’t feel you can’t just because it isn’t in the current sprint.
Please see the issues below and their allocations...
As I said, anything that has Core/Community is up for grabs by anyone, the core team will only tackle them if we have time and no one in the community has picked them up. And same goes for those identified as Community… Though we also wanted to encourage ownership of these so we won’t touch them unless we feel they can’t progress without our intervening.
We have already begun to allocate the above issues out to their specific sprints with aim to show what is currently being worked upon and those issues that need to be tested, reviewed and successfully merged in.
Just to re-iterate from my earlier posts, that the core team do have other tasks that may not be identified in the above sprints and these are usually from our own internal backlog i.e. improving the release process, CI/CD tools (Travis
Now this is all well and good to start, but I guess the underlying part here we need is your help. We, the core team will strive to achieve, at a minimum, what as has been allocated to us, but we would love to see others in contributing to complete this EOL. Any sort of participation would be grand: developing a fix for the above issues, testing any Prs, providing your feedback, help troubleshoot, write up documentation! ANYTHING as long as we are working together to make a successful upgrade that those will feel confident to jump up to the latest versions of SuiteCRM.
Lets do this !
@Abuelodelanada Lets not add too much what is already added unless the Community are willing to jump on them.
Just to remind the community if you are available to help test or develop some of these sprint tasks that are in the TO DO & REVIEW especially if anyone in our partners & development community able to jump on any of the "Help wanted" items.
Just mention ourselves and we can assign a task to yourself :D