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

Discussion: SuiteCRM 7.8.x end-of-life #7294

Closed
pgorod opened this issue May 16, 2019 · 8 comments

Comments

@pgorod
Copy link
Contributor

commented May 16, 2019

Dear SuiteCRM Community members:

As the scheduled end-of-life (EOL) of the 7.8.x LTS version is fast approaching, we’d like to open up a Community discussion on the challenges you currently have with upgrading away from 7.8.

This issue here on GitHub is just a way of calling attention to the discussion that is taking place on the Forums:

https://suitecrm.com/suitecrm/forum/suitecrm-7-0-discussion/24652-suitecrm-7-8-x-reaching-its-end-of-life

  • Please read the full thread on the forums and participate there!

I will be doing a few mentions here (since the Forums unfortunately don't have a mention mechanism) to make sure people receive an email and take the opportunity to participate. Thanks in advance for any input.

@pgorod

This comment has been minimized.

Copy link
Contributor Author

commented May 16, 2019

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.

@horus68
@ApatheticCosmos
@mikebeck
@amariussi
@likhobory
@urdhvatech
@Mausino
@jakubpas
@JanSiero
@lazka
@jsamelko
@adriangibanelbtactic
@ChangezKhan
@Abuelodelanada
@hieuhoanghd
@LionelBino
@vladbar
@sanchezfauste
@adamjakab
@isleshocky77
@anhnhatuit
@ghermans
@eggsurplus
@javitoron
@sathishsengodan
@jobst
@bluquet
@connorshea
@gitbnw
@604media

@Mausino

This comment has been minimized.

Copy link
Contributor

commented May 17, 2019

Thanks for opportunity to add my opinion.. first i apologize for English.

Main changes between version 7.8 and 7.10 are as you wrote

  • Refined SuiteP theme - New Slimmed down SuiteP Design.
  • 4 SuiteP colour schemes - Pick a range of different colour schemes to suit your workspace.
  • New REST API - A new Rest API (v8) using the popular JSONAPI specifications.
  • Survey Management - A new module that will provide you the ability to create, design and send surveys to your customers.
  • Confirmed Opt-In - A new feature that has been introduced to assist CRM users with the European GDPR legislation.
  • 2 Factor Authentication
  • Improved Alerts Functionality
  • Improved Password Management
  • Additional password restrictions, logging to identify login attempts and enforce password requirements.
  • Fail2Ban Logging Integration
  • New Suite of Unit Tests
  • Improved Email Performance
  • Email Fixes

As you can see SaleAgility Team battle against in many levels...

I give reasons why upgrade

  • GDPR legislation... sorry if you're from EU you have no choose if you want be in law
  • New Theme - as everybody know.. we are few years in world mobile first.
  • REST API - if you want connect with world.. no other way.. now every new build applications are API first
  • Unit Tests - i hate them, you hate them.. but without them the large projects will sink

I give you reasons why you shouldn't upgrade

- New Theme P
-- is unusable for my company in mobile. For 95% i'm using for detail view + sub-panels in mobile browser "web for pc view" and zooming... because if i see in Suite P first column of default view + name of record... i feel stupid... zooming is better for me as see 2 fields to record...
-- please should have records in list view the + sign as is used for sub-panels that i don't still need to go to detail view of record..
-- we need have own view for mobile and we must have option which columns we wan see on mobile (minimal for list view + sub-panels) and options what type of data will see when we click on + sign in front of record in row
-- when we want improve something in theme.. is nightmare.. no documentation.. (i am not talking about colors... but view ports or custom elements in theme)

- New Email module...
-- introduced was in 7.9.. total disaster on begun. in 7.10. smaller disaster... when i put to GitHub word EMAIL i see that 209 issues have something with this module where are issues.
-- in my heart i hoped that 7.11 will again big pressure to fix email child problems.... but tramtada... we introduced Google Calendars + Elastic Search ... and minimal pressure on email bugs.. many bugs came back again, which was fixed in 7.10.
-- i told many times.. if you working with emails as one of most important module... stay on 7.8 future unsupported LTS because your business will die... because new email module 7.10 or 7.11 is only 40% of what you can do in 7.8.

Do you want know what child problems are still in latest 7.10 or 7.11 versions???
--- delete email... yes, you can't... why... don't know.. we have ACL (security suite which also isn't working in SuiteCRM) for preventing on it if somebody scare.. sorry use other software or service
--- attachments in non imported emails - you want see what attachments you got... no you can't - first import email and after you'll see that 90% of attachments are only images of signatures of senders. you want see the attachments??.. sorry use other software or service
--- filtering... you can't filter more inboxes or folders.. you can only default and no more.. sorry use other software or service
--- slow performance of query for emails... take tons of time to work with this module... if you want be more productive... sorry use other software or service
--- Run Email Notification is running but no notification is being sent... yes you can create meeting or task or whatever.. can you receive email notification? sorry..
--- Auto Import of Emails not working...

In last year we started discussion about that many users are frustrated from system that community was "ignored" and SalesAgility created great event Pull Request Party (don't know when will next one.. hoped that will minimum ones in every quart of year) and changed some ways how they communicate in this year with community . Now things moved forward and now we have milestones, better labels, and big pressure on API bug fixing.

Maybe in few months will come SuiteCRM 8.. what we know?

  • Angular UI
  • Service Enriched REST API
  • General Framework Modernization and Performance Improvements
  • Fully automated testing for all new code
  • Community Engagement

What we don't know

  • Backwards Compatibility (where possible)
  • New/Enhanced Extendable framework – easier third party development

If many developers will have answers on this 2 unknown details about backward + extendable framework.. they will know if need to spend time that will needed on upgrade for 7.10 LTS or simply go direct to 8.1 LTS.

Sorry is late night and i wrote from heart...

@kelly-walker

This comment has been minimized.

Copy link

commented May 17, 2019

@hubyhuby

This comment has been minimized.

Copy link

commented May 20, 2019

Hi there,
I feel the same.
I have opened an issue on email test coverage.
In my opinion this is the biggest challenge we are facing : having a very stable email function.
Automated Test code coverage is an important to boot with : #7299

@amariussi

This comment has been minimized.

Copy link
Contributor

commented May 23, 2019

I agree with @Mausino on all points except the comments on GDPR: double opt-in is not compulsory and many companies have not adopted it so, in order to be compliant, SuiteCRM should only give an option to adopt it. The way in which it has been implemented makes it compulsory and is both against GDPR and the way in which several companies operate!

@connorshea

This comment has been minimized.

Copy link
Contributor

commented May 24, 2019

The biggest problem thus far (upgrading from 7.9 to 7.10) was probably the theme changes, but for the most part they didn't break too much and only required a few changes for us. Thankfully, we implemented a system where if we modify any core files we mark the changes with a big comment block that explains the change and links to any relevant issues/PRs/commits.

/**
 * CUSTOMIZATION NOTE
 * The change in this file was backported from 7.10.7, see <GitHub commit link> for more info.
 * We can use the upstream file once we've upgraded to 7.10.7+
 */
Code.goes_here()
/**
 * END CUSTOMIZATION NOTE
 */

This made the upgrade process – where I go through each changed file that we've customized and determine whether the upgraded file needs to be modified to preserve any of our customizations – a lot faster. Only took maybe 4-5 hours of work, compared to multiple days of tedious work when upgrading from 7.9.4 to 7.9.17 before this system was in place.

The test coverage is definitely a sore spot for me too, but ultimately the security fixes, new features, and upstream support are important enough that the risk is mostly worth it. We'd definitely appreciate improved test coverage so we can be more confident in the upgrades not having hidden bugs :)

I've also had some trouble determining whether issues were fixed in 7.10 or only in 7.11, e.g. #5173 which doesn't mention any specific version, and which I'm experiencing on 7.10.16.

@pgorod

This comment has been minimized.

Copy link
Contributor Author

commented May 27, 2019

Ok, thanks everyone for their input. I will be going through all this tomorrow and I will try to summarize it.

Then we can try to plan what can be worked on before the EOL date. We'll keep you all updated and involved. Thanks!

@samus-aran

This comment has been minimized.

Copy link
Contributor

commented Jun 8, 2019

Closing this issues (as it has served it purpose!) Thanks everyone who commented. Please see latest discussion thread #7358

@samus-aran samus-aran closed this Jun 8, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
8 participants
You can’t perform that action at this time.