![]() ![]() Simply because nobody is building that right now. But it's far from being a cohesive easy-to-deploy product. You can piece components together (yay, standards!) and I did exactly this for the IETF's XMPP deployment recently. I don't think there are any serious "self-hosted Slack-like" contenders that are XMPP-based right now. The problem is that XMPP and Matrix are protocols, not products.Įlement (the primary Matrix software) definitely has Slack and Discord in its sights. than in changing an existing query's behavior or implementation.) (We generally don't do this for net new functionality there's lower risk in adding a new REST endpoint etc. This also enables us to roll back the dynamic config quickly if something unexpected happens. Our team usually rolls out non-feature changes to services via dynamic configuration switches, so that we can get new bits in place, and then enable new behavior without a redeploy. ![]() ![]() But features are widely used by customers ahead of that time, as part of the rollout process. The feature enablement happens through an EFT / beta process, and the final timing of GA enablement is a PM decision. Our team typically deploys between 10am and 4ish, local time, since that's when we're at our desks and ready to click through the approvals and monitor the changes as they go through our pipelines. The engineering team is responsible for the mess caused by a bad deploy, so it's appropriate that those engineers should also choose the timing. At Cisco (Webex team), the engineers decide when to release code, and most features are enabled by configs or feature flags independently of the deploys. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |