Suitecrm: Sprint Planning (20)

Created on 26 Sep 2019 · 7Comments · Source: salesagility/SuiteCRM

Hello Everyone! :wave:

We are 1 week away from commencing our Sprint. So we would like to take this opportunity to ask for your nominated issues here in this thread so we can assess, refine and coordinate with ourselves (the Core Team) and the community contributors on the upcoming priorities.

If you are new to this sprint planning then essentially we are asking you, as the users, to post your issues (by referencing the GitHub hash/ID) that you would like to see being tackled. We, the Core Team, will review and select the achievable ones within the sprint and allocate them among ourselves. The others we may label them as Help Wanted which would make them up for grabs by our community code contributors. This process will help encourage ownership of these bugs and their bug fixes. Find out more of the sprint concept here :point_left:

Sprints are every 2 weeks with the aim to deliver a release every 2 Sprints (monthly).

Just to re-iterate from previous 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, security patches etc so that accounts for some ‘slack’ visible in the public sprints.

Look forward to your nominations! :writing_hand:

Discussion

Source

Dillon-Brown

Most helpful comment

While I am not going to list specific Issues (Dillon can select them better than me), I would like to see a sustained focus on Email issues. I am also hoping the PR parties can be especially concerned with the robustness of the Email module, and then Campaigns. Thanks

pgorod on 26 Sep 2019

👍2

All 7 comments

Here are the issues/PRs that I'd like to bring attention to:

#7807 (State Checker removal) <= by far the most important to me.
#7808 (config.test.php)
#7771 (dotenv)
#7900 (aow_utils.php notice fix) <= An easy one since I'm merciful
#7879 (Phone fields as links) <= Relatively easy
#7463 (Drop PHP 5.5 support)

EDIT:

I also wanted to add the Sentry PR here, since I contributed to it a decent bit: #7873

connorshea on 26 Sep 2019

👍1

pgorod on 26 Sep 2019

👍2

#7878 to solve the issue with long dropdown lists in workflows' conditions . A similar issue happens on reports. It doesn't require to much work. Just change the lengthen of the field value. I have manually changed it on my installation and it hasn't broke anything so far. Thanks.

AlxGr-OS on 26 Sep 2019

I hope that somebody looks on Email Filtering RFC (Request for Comments) 🗣️ #7725
Because nobody comments there the @samus-aran "roadmap" of Email Filtering

I'm suggesting.. that should we also filter in the future by API calls :)