I remember seeing that “400min cap on ci minutes” banner a while ago, thinking that since we have our own runners, it’s not something we have to worry about.
I just found about the users limit completely by accident, I use Gitlab daily and have not seen any notifications regarding this, and this is a month after it was initially scheduled to take effect.
The way these changes are handled and especially the communication aspect is very unprofessional, and while you say that this was not planned, maybe you didn’t plan for this exact change, but now there is absolutely no doubt in my mind that locking people into your platform and then trying to force them into paid tiers by removing features and changing limits is part of your plan.
It’s very hard not to speculate that you push the proper announcements of this change, simply to force people to change to your paid plan because they won’t have time to properly migrate to another provider when the notification eventually go out, and then hoping they will not bother changing since they at that point are already paying.
You say it will affect less than 2% of your users? All the people complaining about your platform simply becoming infeasible to use begs to differ. It looks like you are simply weeding out the users that you don’t expect to be able to convert into paying customers.
And that it causes significant costs? CI build minutes? - We have our own runners.
Put some limits on whatever causes you significant costs.
It’s fortunate that my company are in a position where we are able to migrate away from your saas offering.
My initial comment was deleted due to a bad word, so I have tried to recreate it from memory…
I do apologize about the inappropriate word usage though.