As it turns out, a better approach to not disturbing our Enterprise edition users is simply keeping all experimental development to the future beta version (currently Synergy 2 Beta). This has many benefits to both business and personal customers previously there were a few bug fixes that only benefited our Enterprise edition users and vice versa, but now everyone gets every bug fix. However, we've found that-paradoxically-they tend to prefer the regular Synergy editions because of the more recent bug fixes that they bring.Īs of Synergy 1.10, we’ve recombined the two forks back into a single codebase. Since 2013, we've onboarded many new business customers who are using the Enterprise edition. Merging fixes between them became risky and eventually, the Enterprise edition codebase started to stagnate. It turned out that the two forks drifted significantly over time, and eventually the Enterprise edition codebase got left behind. However, there was a drawback to that approach. The benefit was that we could make any changes we wanted in the non-enterprise version without disturbing our new customer. There were some deployment and security requirements that we hadn't yet thought of, which we soon addressed.Īfter finding out what we needed to do for our new client, we decided that we should maintain 2 codebases for Synergy an Enterprise edition codebase and a separate codebase for the regular editions (Pro and Basic). Our first trip to The Steve Jobs Building on the Pixar campus was pretty exciting as it gave us some really interesting insight into how a larger company uses Synergy. As a budding software company and team of two, we leapt at the opportunity to work with the infamous animation studio from Emeryville, California.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |