<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Wed Feb 07 21:12:12 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>MongoDB Jira</title>
    <link>https://jira.mongodb.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.7.1</version>
        <build-number>970001</build-number>
        <build-date>13-04-2023</build-date>
    </build-info>


<item>
            <title>[CDRIVER-1337] Add configure flag for unstable MongoDB 3.4 support</title>
                <link>https://jira.mongodb.org/browse/CDRIVER-1337</link>
                <project id="10030" key="CDRIVER">C Driver</project>
                    <description>&lt;p&gt;Add a configure flag to libbson and libmongoc&apos;s Autotools and CMake build systems, something like &lt;tt&gt;--enable-experimental-features&lt;/tt&gt; that is off by default, undocumented, and enables decimal128 and other MongoDB 3.4 features in the C Driver on master. Unhide these features for the 1.5 release.&lt;/p&gt;</description>
                <environment></environment>
        <key id="294872">CDRIVER-1337</key>
            <summary>Add configure flag for unstable MongoDB 3.4 support</summary>
                <type id="2" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14711&amp;avatarType=issuetype">New Feature</type>
                                            <priority id="3" iconUrl="https://jira.mongodb.org/images/icons/priorities/major.svg">Major - P3</priority>
                        <status id="6" iconUrl="https://jira.mongodb.org/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="9">Done</resolution>
                                        <assignee username="jesse@mongodb.com">A. Jesse Jiryu Davis</assignee>
                                    <reporter username="jesse@mongodb.com">A. Jesse Jiryu Davis</reporter>
                        <labels>
                    </labels>
                <created>Fri, 17 Jun 2016 20:18:22 +0000</created>
                <updated>Mon, 8 Aug 2016 18:57:50 +0000</updated>
                            <resolved>Mon, 8 Aug 2016 18:57:49 +0000</resolved>
                                    <version>1.4.0</version>
                                    <fixVersion>1.4.0</fixVersion>
                                    <component>Build</component>
                                        <votes>0</votes>
                                    <watches>4</watches>
                                                                                                                <comments>
                            <comment id="1350550" author="jesse" created="Mon, 8 Aug 2016 18:57:50 +0000"  >&lt;p&gt;Closing unless anyone objects to the current solution.&lt;/p&gt;</comment>
                            <comment id="1349096" author="bjori" created="Fri, 5 Aug 2016 21:23:53 +0000"  >&lt;p&gt;I&apos;m fine with hiding it from our configure flags. The original idea was to have it totally hidden and require manually adding it to your CFLAGS before running ./configure. That idea proved difficult because we have to export different symbols, along with various tedious details.&lt;/p&gt;

&lt;p&gt;I can&apos;t think of a way to remove it from the ./configure --help listing, while keeping it as a supported flag. Is that possible?&lt;/p&gt;

&lt;p&gt;Trying to extract an actionable item from your comment, best I can suggest is to add extra experimental disclaimer when using the flag?&lt;br/&gt;
It already says its experimental, but we can throw in some caps and stronger language?&lt;/p&gt;

&lt;p&gt;Since humans don&apos;t edit the mongoc-config.h, I&apos;m not sure what difference it makes if its called &lt;tt&gt;__MONGOC_INTERNAL_EXPERIMENT&lt;/tt&gt; or &lt;tt&gt;MONGOC_EXPERIMENTAL&lt;/tt&gt;. If you think its worth the change in mongoc, libbson, phpc, and the outstanding c++11 PR, then.. ok.&lt;/p&gt;</comment>
                            <comment id="1349039" author="david.golden" created="Fri, 5 Aug 2016 20:29:57 +0000"  >&lt;p&gt;After some reflection and discussions with &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=acm&quot; class=&quot;user-hover&quot; rel=&quot;acm&quot;&gt;acm&lt;/a&gt; and &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=jesse&quot; class=&quot;user-hover&quot; rel=&quot;jesse&quot;&gt;jesse&lt;/a&gt;, and following the principle of &quot;strong opinions, lightly held&quot;, I&apos;ve come around to a different way of thinking:&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;The C++11 driver will be using a development branch for its version 3.1 (with MongodB 3.4 features).  It won&apos;t merge to master until after libmongoc 1.5 ships.  Therefore, it doesn&apos;t need to use any conditional macros of its own or from libmongoc.&lt;/li&gt;
	&lt;li&gt;The reason we need conditional macros in libmongoc is so that &lt;b&gt;during development&lt;/b&gt; we can test the C++11 3.1 branch against a libmongoc with those symbols available.&lt;/li&gt;
	&lt;li&gt;Effectively, the libmongoc flag is just a &lt;b&gt;developer tool&lt;/b&gt; to enable some symbols (in lieu of all 3.4 work in libmongoc being on a dev branch) so we can build and test before libmongoc 1.5 is stable. It does not need to be consumed by general downstream users.&lt;/li&gt;
	&lt;li&gt;If it&apos;s not going to be consumed by downstream users, then we shouldn&apos;t use feature flags as a mental model.  It should be coarse-grained and called &quot;experimental&quot; or even something more arcane and off-putting.  (e.g. &lt;tt&gt;__MONGOC_INTERNAL_EXPERIMENT&lt;/tt&gt;) It should be documented with strong warnings so that downstream users don&apos;t depend on it.&lt;/li&gt;
&lt;/ul&gt;
</comment>
                            <comment id="1347397" author="bjori" created="Thu, 4 Aug 2016 17:36:24 +0000"  >&lt;p&gt;I don&apos;t think its a good idea.&lt;br/&gt;
C++11 r3.1.0 will then unintentionally conditionally have MongoDB 3.4 support.&lt;/p&gt;

&lt;p&gt;I think it needs to be deliberate decision if C++11 r3.1.0 has MongoDB 3.4 support or not. Not &quot;maybe&quot; and &quot;it depends&quot;.&lt;/p&gt;

&lt;p&gt;No driver should ship production ready driver with experimental features enabled by default. But thats effectively what happens when the feature macro is kept around for 1.5, then the experimental code in C++11 r3.1.0 that was work-in-progress suddenly has hardcoded 3.4 support which isn&apos;t complete.&lt;/p&gt;
</comment>
                            <comment id="1347314" author="jesse" created="Thu, 4 Aug 2016 16:34:31 +0000"  >&lt;p&gt;Like I said, MONGODB_34_EXPERIMENTAL &quot;is off by default in 1.4.0, In 1.5.0 it&apos;s on and you can&apos;t turn it off.&quot; It won&apos;t be removed.&lt;/p&gt;</comment>
                            <comment id="1347277" author="bjori" created="Thu, 4 Aug 2016 16:04:20 +0000"  >&lt;p&gt;I&apos;m not sure what &lt;tt&gt;#1&lt;/tt&gt; solves? If we remove the &lt;tt&gt;MONGODB_34_EXPERIMENTAL&lt;/tt&gt; their code still won&apos;t work, so we&apos;d have to keep it around forever or remove it &quot;&lt;tt&gt;in a very coordinated&lt;/tt&gt;&quot; way.&lt;/p&gt;

&lt;p&gt;In related note: When we originally added this I was in favor of independent flags, and still am. But it doesn&apos;t resolve the issues pointed out (which I don&apos;t think are issues).&lt;/p&gt;

&lt;p&gt;The experimental flag is meant to be removed. Drivers using it are meant to remove it. It is meant as a one off batch of things that dependent drivers can start playing with, breaking, and developing initial support. Dependent drivers CANNOT advertise availability of these features behind experimental. We have to get these features out to dependent drivers as early as we can to give them the chance to work with them with plenty of time before &lt;tt&gt;MongoDB 3.4&lt;/tt&gt;. Releasing them last week of Q3 when the server ships is cruel.&lt;/p&gt;

&lt;p&gt;Once time comes for us to ship our, and dependent drivers, &lt;tt&gt;MongoDB 3.4&lt;/tt&gt; compatibility releases, the flag will be removed and dependent drivers are expected to remove the check and then announce its availability.&lt;/p&gt;

&lt;p&gt;I have no issue with the &lt;tt&gt;code churn&lt;/tt&gt;. It is removal of a code block that declared it experimental and intentionally promoting it to be fully valued feature of the driver, or removing the feature completely as it didn&apos;t make the cut for &lt;tt&gt;MongoDB 3.4&lt;/tt&gt;.&lt;/p&gt;

&lt;p&gt;Still checking for &lt;tt&gt;MONGOC_34_FEATURES&lt;/tt&gt; or &lt;tt&gt;MONGOC_EXPERIMENTAL_HANDSHAKE_DATA&lt;/tt&gt; when the feature has been removed, or dramatically changed for &lt;tt&gt;MongoDB 3.6&lt;/tt&gt; so we&apos;d have to change the API isn&apos;t going to help you much.&lt;/p&gt;

&lt;p&gt;And if we unconditionally would set the &lt;tt&gt;MONGOC_34_FEATURES&lt;/tt&gt; flag in 1.5, the features would accidentally be promoted to fully qualified features in the dependent drivers in versions they had no intentions of supporting 3.4.&lt;/p&gt;</comment>
                            <comment id="1347157" author="david.golden" created="Thu, 4 Aug 2016 14:46:46 +0000"  >&lt;p&gt;Bikeshed for #1: How about calling it &lt;tt&gt;MONGODB_34_FEATURES&lt;/tt&gt; instead of &lt;tt&gt;MONGODB_34_EXPERIMENTAL&lt;/tt&gt;.  I.e. coarse-grained features rather than &quot;experimental&quot;.  It&apos;s going to be weird to see &quot;experimental&quot; locked on after it&apos;s not experimental anymore and this way even after depending on 1.5.0, we can just leave the flag alone.&lt;/p&gt;</comment>
                            <comment id="1347130" author="jesse" created="Thu, 4 Aug 2016 14:37:35 +0000"  >&lt;p&gt;Hannes, would you be willing to do this?&lt;/p&gt;

&lt;p&gt;Various people have suggested that instead of a general &quot;experimental&quot; flag, we should have specific feature flags. &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=david.golden&quot; class=&quot;user-hover&quot; rel=&quot;david.golden&quot;&gt;david.golden&lt;/a&gt; convinced me &lt;a href=&quot;https://github.com/mongodb/mongo-cxx-driver/pull/509#issuecomment-237430189&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;in a GitHub comment&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;I have two proposals:&lt;/p&gt;

&lt;p&gt;Proposal one. Rename the flag MONGODB_34_EXPERIMENTAL. It&apos;s off by default in 1.4.0, In 1.5.0 it&apos;s on and you can&apos;t turn it off. Downstream drivers can #ifdef MONGODB_34_EXPERIMENTAL for now. Once they depend on 1.5.0 they can remove their ifdefs.&lt;/p&gt;

&lt;p&gt;We can continue to step forward like this in the future: MONGODB_36_EXPERIMENTAL and so on.&lt;/p&gt;

&lt;p&gt;I like proposal one because it&apos;s easy for us to search-and-replace our whole codebase, and it&apos;s easy for downstream drivers to search-and-replace theirs, instead of doing finicky work for each feature.&lt;/p&gt;

&lt;p&gt;Proposal two. Feature flags:&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;BSON_EXPERIMENTAL_DECIMAL128&lt;/li&gt;
	&lt;li&gt;MONGOC_EXPERIMENTAL_COMMANDS_WRITE_CONCERN&lt;/li&gt;
	&lt;li&gt;MONGOC_EXPERIMENTAL_HANDSHAKE_DATA&lt;/li&gt;
	&lt;li&gt;MONGOC_EXPERIMENTAL_MAX_STALENESS&lt;/li&gt;
&lt;/ul&gt;
</comment>
                            <comment id="1337844" author="xgen-internal-githook" created="Wed, 27 Jul 2016 16:56:06 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{u&apos;username&apos;: u&apos;ajdavis&apos;, u&apos;name&apos;: u&apos;A. Jesse Jiryu Davis&apos;, u&apos;email&apos;: u&apos;jesse@mongodb.com&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/CDRIVER-1337&quot; title=&quot;Add configure flag for unstable MongoDB 3.4 support&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CDRIVER-1337&quot;&gt;&lt;del&gt;CDRIVER-1337&lt;/del&gt;&lt;/a&gt; disable aggregate_with_write_concern&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo-c-driver/commit/f9425f38e4acfb50c470a8605b655d83af5c0d7e&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo-c-driver/commit/f9425f38e4acfb50c470a8605b655d83af5c0d7e&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="1330718" author="xgen-internal-githook" created="Wed, 20 Jul 2016 23:56:35 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{u&apos;username&apos;: u&apos;ajdavis&apos;, u&apos;name&apos;: u&apos;A. Jesse Jiryu Davis&apos;, u&apos;email&apos;: u&apos;jesse@mongodb.com&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/CDRIVER-1337&quot; title=&quot;Add configure flag for unstable MongoDB 3.4 support&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CDRIVER-1337&quot;&gt;&lt;del&gt;CDRIVER-1337&lt;/del&gt;&lt;/a&gt; fix decimal128 JSON test&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/libbson/commit/7fcb9573290ab62f34d4755850f616141d1be231&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/libbson/commit/7fcb9573290ab62f34d4755850f616141d1be231&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="1330717" author="xgen-internal-githook" created="Wed, 20 Jul 2016 23:56:34 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{u&apos;username&apos;: u&apos;ajdavis&apos;, u&apos;name&apos;: u&apos;A. Jesse Jiryu Davis&apos;, u&apos;email&apos;: u&apos;jesse@mongodb.com&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/CDRIVER-1337&quot; title=&quot;Add configure flag for unstable MongoDB 3.4 support&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CDRIVER-1337&quot;&gt;&lt;del&gt;CDRIVER-1337&lt;/del&gt;&lt;/a&gt; completely disable decimal by default&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/libbson/commit/03284d18bd67f52a69d50c07c9b60f0c83adec19&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/libbson/commit/03284d18bd67f52a69d50c07c9b60f0c83adec19&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="1330406" author="jesse" created="Wed, 20 Jul 2016 19:21:16 +0000"  >&lt;p&gt;Need to disable BSON_ITER_HOLDS_DECIMAL128, VISIT_DECIMAL128.&lt;/p&gt;</comment>
                            <comment id="1327564" author="xgen-internal-githook" created="Mon, 18 Jul 2016 20:46:06 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{u&apos;username&apos;: u&apos;ajdavis&apos;, u&apos;name&apos;: u&apos;A. Jesse Jiryu Davis&apos;, u&apos;email&apos;: u&apos;jesse@mongodb.com&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/CDRIVER-1337&quot; title=&quot;Add configure flag for unstable MongoDB 3.4 support&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CDRIVER-1337&quot;&gt;&lt;del&gt;CDRIVER-1337&lt;/del&gt;&lt;/a&gt; disable additional maxStalenessMS features&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo-c-driver/commit/ba6c17e32e4fe419eaccd1f76abfea7f6208d6e2&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo-c-driver/commit/ba6c17e32e4fe419eaccd1f76abfea7f6208d6e2&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="1327463" author="xgen-internal-githook" created="Mon, 18 Jul 2016 19:41:49 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{u&apos;username&apos;: u&apos;ajdavis&apos;, u&apos;name&apos;: u&apos;A. Jesse Jiryu Davis&apos;, u&apos;email&apos;: u&apos;jesse@mongodb.com&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/CDRIVER-1337&quot; title=&quot;Add configure flag for unstable MongoDB 3.4 support&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CDRIVER-1337&quot;&gt;&lt;del&gt;CDRIVER-1337&lt;/del&gt;&lt;/a&gt; disable maxStalenessMS by default&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo-c-driver/commit/dba96fbdf9a0008eaa978f72650a6845adc4dab0&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo-c-driver/commit/dba96fbdf9a0008eaa978f72650a6845adc4dab0&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="1323497" author="xgen-internal-githook" created="Thu, 14 Jul 2016 00:38:05 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{u&apos;username&apos;: u&apos;ajdavis&apos;, u&apos;name&apos;: u&apos;A. Jesse Jiryu Davis&apos;, u&apos;email&apos;: u&apos;jesse@mongodb.com&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/CDRIVER-1337&quot; title=&quot;Add configure flag for unstable MongoDB 3.4 support&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CDRIVER-1337&quot;&gt;&lt;del&gt;CDRIVER-1337&lt;/del&gt;&lt;/a&gt; disable experimental features by default&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo-c-driver/commit/887ed7e05e6cd23991e55382a8a2a4e2c96b0676&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo-c-driver/commit/887ed7e05e6cd23991e55382a8a2a4e2c96b0676&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="1316957" author="xgen-internal-githook" created="Thu, 7 Jul 2016 16:02:16 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{u&apos;username&apos;: u&apos;ajdavis&apos;, u&apos;name&apos;: u&apos;A. Jesse Jiryu Davis&apos;, u&apos;email&apos;: u&apos;jesse@mongodb.com&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/CDRIVER-1337&quot; title=&quot;Add configure flag for unstable MongoDB 3.4 support&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CDRIVER-1337&quot;&gt;&lt;del&gt;CDRIVER-1337&lt;/del&gt;&lt;/a&gt; build libbson with experimental features&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo-c-driver/commit/3fb2dc4feedb36ea2f5980ebf675c82603075995&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo-c-driver/commit/3fb2dc4feedb36ea2f5980ebf675c82603075995&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="1316875" author="xgen-internal-githook" created="Thu, 7 Jul 2016 15:32:33 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{u&apos;username&apos;: u&apos;ajdavis&apos;, u&apos;name&apos;: u&apos;A. Jesse Jiryu Davis&apos;, u&apos;email&apos;: u&apos;jesse@mongodb.com&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/CDRIVER-1337&quot; title=&quot;Add configure flag for unstable MongoDB 3.4 support&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CDRIVER-1337&quot;&gt;&lt;del&gt;CDRIVER-1337&lt;/del&gt;&lt;/a&gt; export all symbols in libbson-experimental.def&lt;/p&gt;

&lt;p&gt;I&apos;d thought specifying two symbol files with CMake&apos;s add_library would&lt;br/&gt;
merge their symbol tables. In fact the last file wins, so all symbols&lt;br/&gt;
must be included in single symbol file.&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/libbson/commit/e1c1516a64a39cc0cb8b9c31b14099a3c926cfb0&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/libbson/commit/e1c1516a64a39cc0cb8b9c31b14099a3c926cfb0&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="1316037" author="xgen-internal-githook" created="Wed, 6 Jul 2016 21:17:31 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{u&apos;username&apos;: u&apos;bjori&apos;, u&apos;name&apos;: u&apos;Hannes Magnusson&apos;, u&apos;email&apos;: u&apos;bjori@php.net&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/CDRIVER-1337&quot; title=&quot;Add configure flag for unstable MongoDB 3.4 support&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CDRIVER-1337&quot;&gt;&lt;del&gt;CDRIVER-1337&lt;/del&gt;&lt;/a&gt; Fix double declaration of BSON_EXPERIMENTAL_FEATURES&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/libbson/commit/50f08b4ed66f52416945f9c49b3a7a24eece3f95&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/libbson/commit/50f08b4ed66f52416945f9c49b3a7a24eece3f95&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="1315881" author="xgen-internal-githook" created="Wed, 6 Jul 2016 19:50:36 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{u&apos;username&apos;: u&apos;ajdavis&apos;, u&apos;name&apos;: u&apos;A. Jesse Jiryu Davis&apos;, u&apos;email&apos;: u&apos;jesse@mongodb.com&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/CDRIVER-1337&quot; title=&quot;Add configure flag for unstable MongoDB 3.4 support&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CDRIVER-1337&quot;&gt;&lt;del&gt;CDRIVER-1337&lt;/del&gt;&lt;/a&gt; define BSON_EXPERIMENTAL_FEATURES&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/libbson/commit/93f788252969c1ba6505fb7f681a91234d09fa90&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/libbson/commit/93f788252969c1ba6505fb7f681a91234d09fa90&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="1315757" author="xgen-internal-githook" created="Wed, 6 Jul 2016 18:10:42 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{u&apos;username&apos;: u&apos;ajdavis&apos;, u&apos;name&apos;: u&apos;A. Jesse Jiryu Davis&apos;, u&apos;email&apos;: u&apos;jesse@mongodb.com&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/CDRIVER-1337&quot; title=&quot;Add configure flag for unstable MongoDB 3.4 support&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CDRIVER-1337&quot;&gt;&lt;del&gt;CDRIVER-1337&lt;/del&gt;&lt;/a&gt; disable future features by default&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/libbson/commit/3dbe26172bad65bf9b5bd9d01e822b7b947ccb6a&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/libbson/commit/3dbe26172bad65bf9b5bd9d01e822b7b947ccb6a&lt;/a&gt;&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="299606">CXX-969</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="274303">CXX-873</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="301583">CDRIVER-1393</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="303263">CDRIVER-1410</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_15850" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hsmmv3:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10558" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>9223372036854775807</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            </customfields>
    </item>
</channel>
</rss>