Topic: Release strategy and 4.x.x version support needs to be addressed ASAP.
Hi David,
I like your product, and i understand what you are going through, but, reading through the forum, i think you need take a step back and address some of the points below.
We will all understand if features come by slower, we can build those features ourselves if we truly need them.
What we can't have is a library stuck on an alpha version of bootstrap on a live site, just because of the sheer amount of breaking changes , new features and bugs introduced with each release you make.
There is absolutely NO migration documentation for any of the 4.x releases. (nothing a coder can use)
You are treating previous releases as throwaways, that needs to stop.
We have production code running those, and that code needs to maintained by a human being.
No more undocumented breaking changes.
The upgrade path for sites built on version 4.0.x is a monster feat for already implemented and tweaked code.
You've changed helper syntax for instance.
You don't announce your plans for the next release.
You don't keep previous branches tagged (PRO) and provide bug fixes for those in an orderly way.
You are feature cramming a library that at this point is screaming for stability, speed and robustness.
You don't inform your clients which areas should be considered stable and which ones should not.
In essence, please take a step back, and figure out a way to provide migration/upgrade 4.x.x to 4.x.x support that matches your release strategy.
If you are not going to have a stable branch until bootstrap is RC, then provide us with tools and data to accompany you on that trip, which is totally fine.
You are building your product on ALPHA, and you are charging for it (PRO)
You need to understand inter release support is expected.
Otherwise, what have we bought?
keep at it. think about this please. it can get worse.
cheers
kik
Add comment
Dear Users,
we owe you a serious apology.
Let me refer all your issues point by point.
We are aware of all the problems caused by the latest releases. We have started to work to address all the issues. Now we are going to focus completely on stability and clarity.
1. "There is absolutely NO migration documentation for any of the 4.x releases"
- We plan to publish it this week.
2. "You are treating previous releases as throwaways, that needs to stop."
- We will, I promise.
3. "No more undocumented breaking changes"
- We really do care to make our documentation as detailed as possible and cover all the changes. If you know any specific, undocumented change - please let me know. I'll find a responsible person and make sure it will not happen again.
4. "You’ve changed helper syntax for instance"
- We didn't. It's Bootstrap changes. But I understand complications caused by these changes and I'll promise we'll take care of it.
5. "You don’t announce your plans for the next release."
- We will, I promise.
6. "You don’t keep previous branches tagged (PRO) and provide bug fixes for those in an orderly way."
- We will, I promise.
7. "You are feature cramming a library that at this point is screaming for stability, speed and robustness."
Unfortunately again, it's mostly Bootstrap changes. But we'll address that issue as well (especially that current Alpha [6] is the last one before Beta version of Bootstrap 4)
8. "You don’t inform your clients which areas should be considered stable and which ones should not."
- We will, I promise.
9. "I just wished you had a git repo where we can help"
- We are going to create repo of MDB Pro for our customers. I hope it will happen yet in February.
10. "Will I have to develop all my frontend side step by step without a proper documentation?"
Right now we are 100% focused on improving that issues and providing you stability you need. That's our only goal for the next months.
At the end I would like to assure you that our entire team right now is prepared to provide any you all the support you need. Any technical question will be answered as soon as possible.
Best Regards and once again I apologize on behalf of the entire MDB team.
Michal
In a way I understand that it will still be a bit unstable, since bootsrap is in Alpha and MDB is built on top of it, thus everytime bootsrap makes major changes, MDB will have to do so as well. And luckily I think bootstrap is in its last Alpha phase before going Beta. Additionally we are not suppose to build any production application on an Alpha version of anything (yet we still do :P ). So in essence I understand the struggles on MDB's side. HOWEVER, as Enrique said, we paid a premium price for the PRO version, hence I just expect more.
I'm really upset with this product. I paid to get a better results in my projects, trying to forget or leave the most complicated things at the frontend side to this product, but as you said, we don't have enough information about how to use or implement the new changes. First, I used the version 4.2 and now when I try to update into 4.3 there are too many changes that has made a mess with my project. I am really worried about the stability of this product, how many times will I get the same result in the future if I tried to incorporate the new fixes in MDB 4? Will I have to develop all my frontend side step by step without a proper documentation?
At this point, I really want to get back my money. It's not stable, the alpha version will be for sure a headache to implement this project. There are too many thing that are so difficult to use because of a poor documentation even in the boostrap 4 project.
Could not agree more with this.
I want to just echo everything that you said. The only thing that I will add is that sometimes I just wished you had a git repo where we can help, because at the moment when I get stuck with something that is not working with your UI Kit, I will spend some time to fix it and get it working, but now either you eventually fix it (which might break my implementation) or you never do and the next developer has to struggle through the same bug.
Put the PRO version on GitHub and just license it correctly, that way we can contribute and still pay for it if we want to use it (based on your license), because I'm sure you are aware that I can download the PRO version for free anycase, it is literally a Google search away.
FREE CONSULTATION
Hire our experts to build a dedicated project. We'll analyze your business requirements, for free.
Status
Specification of the issue
- ForumUser: Pro
- Premium support: No
- Technology: General Bootstrap questions
- MDB Version: -
- Device: -
- Browser: -
- OS: -
- Provided sample code: No
- Provided link: No
Tags