<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Bosco Jacinto on Medium]]></title>
        <description><![CDATA[Stories by Bosco Jacinto on Medium]]></description>
        <link>https://medium.com/@boscojacinto?source=rss-6d55ec20624b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*YB-k-L68FKs-jXIe.</url>
            <title>Stories by Bosco Jacinto on Medium</title>
            <link>https://medium.com/@boscojacinto?source=rss-6d55ec20624b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 09:47:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@boscojacinto/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Why customer release software versioning is mostly NOT sequential ?]]></title>
            <link>https://medium.com/@boscojacinto/why-customer-release-software-versioning-is-mostly-not-sequential-ea707435f110?source=rss-6d55ec20624b------2</link>
            <guid isPermaLink="false">https://medium.com/p/ea707435f110</guid>
            <category><![CDATA[releases]]></category>
            <category><![CDATA[version-control]]></category>
            <category><![CDATA[release-management]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Bosco Jacinto]]></dc:creator>
            <pubDate>Tue, 21 Mar 2017 17:59:15 GMT</pubDate>
            <atom:updated>2017-03-21T17:59:15.257Z</atom:updated>
            <content:encoded><![CDATA[<h4>We stumbled across a request today… customer release versioning should to be sequential!!</h4><p>That’s difficult to do and most NOT practiced industry wide. This blog “<a href="http://inedo.com/blog/how-to-create-version-numbers-that-are-actually-semantic">how-to-create-version-numbers-that-are-actually-semantic</a>” explains different numbering schemes and why sequential is not so good.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/715/1*fYZwvNsKZVSWA8qGHtCNhA.jpeg" /><figcaption>Sequential version numbering scheme</figcaption></figure><h3>Some background</h3><p>We use the scheme “Major.Minor.Feature.Revision”. This is a little different than “Major.Minor.Revision”, the addition of Feature no. allows us to identify the set of features that goes along the release (in this case all features from 1 to 12 are present). As an example “5.20.12.1”.</p><p>Feature branches are created with an extra dot separated identifier i.e 5.20.11.25.<strong>1</strong> for developers and testers to identify a developer branch release. When the feature matures and passes QA it is merged into the master and a QA is done again. The advantage of Feature number is that certain bug symptoms can be easily traced to a feature addition.</p><p>The following diagram is a representation of the above version numbering system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b6CSxKbeTs_piLKWV7FZuQ.jpeg" /></figure><h3>Why is it difficult?</h3><p>Paying customers are their own boss, aren’t they? Not exactly because they are not the only paying customer, for example: If WhatsApp had only one paying customer i.e you, wouldn’t you want every update of their app to have a simple sequential version numbering scheme (i.e 2.17.24 to 2.17.25). Instead it changes from 2.17.24 to 2.17.104 in the last recent update. This is because you are not the only customer and updates are not rolled out as per your liking. This becomes especially difficult when you deal with multiple OEM’s as your customers.</p><h3>Developer’s Cycle (sprint) and Customer’s Cycle</h3><p>Developer’s move fast, OEM’s don’t. Rapid development and fast iteration is essential in customer facing software, we all like more features and quick bug fixes in our software. OEM’s move with their own pace, that shouldn’t hamper software development efforts (in most cases having a dedicated branch for them solves this issue).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CR0GhyG6FPAtguV9u233wA.jpeg" /><figcaption>Customer’s cycle and Developer’s cycle</figcaption></figure><p>When a developer is done with a feature/bug-fix/enhancement it goes through the developer cycle once and is eligible as a release candidate to the Release Manager. The gif below shows one developer cycle.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*8vGyuERQOPHxt_9oPgv0jw.gif" /><figcaption>Developer’s Cycle (sprint)</figcaption></figure><p>If the Release Manager decides to push the release to the customer then it becomes a Customer release. One Customer cycle is shown below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SyFvDcqDthRr6QX6KHIx-A.jpeg" /><figcaption>Customer’s cycle</figcaption></figure><p>The developer continues with the next cycles (sprints) and adds to the release candidate list. All this while there is no customer releases scheduled (with the exception of the last slide in the gif below).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*RM2PhjXHILC50MQIq1AyMQ.gif" /><figcaption>Developer’s cycle faster than Customer release</figcaption></figure><p>So far we’ve had 4 release candidates out of which 2 were customer releases as shown below (in red).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eP8dtVJqAUZds8GHoCkXdg.jpeg" /><figcaption>Customer Release’s</figcaption></figure><h3>Forcing Sequential versioning</h3><p>To have sequential versioning in the above system you’ll need a painful mapping strategy. In short every customer release will have to be mapped to the current release candidate. The customer version number will move independent (of-course sequentially) of the release candidate versioning. This means that 5.20.11.28 (next sequential customer release after 5.20.11.27) would map to 5.20.11.30 (release candidate).</p><p>This mapping would need to be as close to the source code as possible, ideally in the same repo as the build. Also to note is that the release candidate versioning is good to have hard-coded in source. This involves an additional step in the developer cycle (sprint) to take care of this mapping, the management of this mapping only gets so more difficult as the number of customer’s/OEM’s increase.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*KpYfXflwGW36ZwOD_Wa4jA.gif" /><figcaption>Painful mapping</figcaption></figure><p>All aspects of the development and testing is affected by this</p><ol><li><strong>Issue reporting</strong>: All customer issues will be reported with customer version number. Tracing this to code will require the overhead of looking up the release candidate version.</li><li><strong>Upgrade complexities</strong>: Backward compatibility will now have two level of checks, one between release candidate versions and the other with customer release versions.</li><li><strong>Human error</strong>: Given the overhead chances for human error increases a magnitude by order. Since the mapping is not in the source (and it can’t be because it introduces one more nested complexity of management) the chances of this entity being handled differently as expected either while upgrade, or while deployment is more.</li></ol><h3>Conclusion</h3><p>Although sequential version numbering is easy to understand for the non-technically folks, its simply not viable and salable in terms of development speed. Even customer facing products have to excuse themselves for not having sequential release numbering which now seems like a very trivial thing to have anyways.</p><p>Want to know how and when Major, Minor and Revision numbers increment read this <a href="http://semver.org/">http://semver.org/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea707435f110" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[For all those criticising Tesla for releasing Autopilot immaturely in turn creating a "false sense…]]></title>
            <link>https://medium.com/@boscojacinto/for-all-those-criticising-tesla-for-releasing-autopilot-immaturely-in-turn-creating-a-false-sense-4897f703f220?source=rss-6d55ec20624b------2</link>
            <guid isPermaLink="false">https://medium.com/p/4897f703f220</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[self-driving-cars]]></category>
            <category><![CDATA[autopilot]]></category>
            <category><![CDATA[cars]]></category>
            <category><![CDATA[tesla]]></category>
            <dc:creator><![CDATA[Bosco Jacinto]]></dc:creator>
            <pubDate>Sat, 02 Jul 2016 19:22:54 GMT</pubDate>
            <atom:updated>2016-07-02T19:30:48.782Z</atom:updated>
            <content:encoded><![CDATA[<p>For all those criticising Tesla for releasing Autopilot immaturely in turn creating a &quot;false sense of safety&quot; in the minds of its users, we do have to understand that new technology relies on early adopters to act as torchbearers. This is also seen in the past when commercial airplanes took to the skies had not the bunch of people adopted this new means of travel, you wouldn’t be comfortable boarding a flight today and inspite of many decades of refinement in flight technology it still inst 100% safe to fly. <br><br>Tesla is pushing the level of technology more than any other car company today, why haven’t it’s competitors thought of eliminating the need of buttons and dials by introducing a touchscreen and why has thought not been given to door handles which just serve function and not style. Instead Tesla introduced a 17 inch centre console at the time when the first gen iPad was just 2 year old and forward presenting retractable door handles which otherwise is flush with the contour of the door (reduces drag by a small margin, imp for an electric car). And most importantly pushing Autopilot to the fleet as a public beta only so to say that it’s not perfect but will get better as training data is gathered in the millions unlike other companies that have just a bunch of mules running on the streets of silicon valley.</p><p>In the aftermath of the Tesla Autopilot crash I really do hope that this doesn’t create a dent in the minds of the government bodies of transport and also in the community as a whole because great technology is good and should not be withheld by lobbyists in protecting hidden government interests. Tesla is an honest and open company at least that’s what’s it seems, doing good and the right things and making the product compelling is what a company should do rather then just focusing on sales and numbers.</p><p>P.S There is lot of complexities related to fully autonomous self driving cars but apart from there is also a <a href="https://youtu.be/ixIoDYVfKA0">mortality question</a> which will be exciting to see as it unfolds in our lifetime.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4897f703f220" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>