<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Wed Feb 07 22:01:08 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>[CXX-1019] Test with latest versions of Boost</title>
                <link>https://jira.mongodb.org/browse/CXX-1019</link>
                <project id="11980" key="CXX">C++ Driver</project>
                    <description>&lt;p&gt;Boost is up to 1.63.  We should test against all recent versions on both Linux and Windows and document (or fix) compatibility.&lt;/p&gt;</description>
                <environment></environment>
        <key id="314591">CXX-1019</key>
            <summary>Test with latest versions of Boost</summary>
                <type id="3" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14718&amp;avatarType=issuetype">Task</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="12300">Won&apos;t Do</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="david.golden@mongodb.com">David Golden</reporter>
                        <labels>
                            <label>bgtrack</label>
                    </labels>
                <created>Wed, 7 Sep 2016 13:43:52 +0000</created>
                <updated>Wed, 18 Jan 2023 19:43:59 +0000</updated>
                            <resolved>Wed, 18 Jan 2023 19:43:59 +0000</resolved>
                                                                    <component>Build</component>
                                        <votes>0</votes>
                                    <watches>3</watches>
                                                                                                                <comments>
                            <comment id="5121825" author="JIRAUSER1269924" created="Wed, 18 Jan 2023 19:43:59 +0000"  >&lt;p&gt;After careful evaluation, we have decided to close this ticket. Please add a comment if the impact of this ticket increases.&lt;br/&gt;
Thanks.&lt;/p&gt;</comment>
                            <comment id="1497218" author="rassi@10gen.com" created="Sat, 11 Feb 2017 01:03:40 +0000"  >&lt;blockquote&gt;
&lt;p&gt;This is going to be tricky, in practice, due to how boost gets installed.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;&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;, to clarify, you mean will this be tricky because Boost is often installed to our standard include paths on our CI machines, yes?&lt;/p&gt;

&lt;p&gt;I spun up a ubuntu1604-build test machine today which has Boost 1.58 installed to /usr/include.  I installed Boost 1.63 to /opt/boost_1_63_0, and verified that -DBOOST_DIR=/opt/boost_1_63_0 correctly caused the driver to build with Boost 1.63, in that the Boost 1.63 directory was indeed searched earlier than /usr/include.  The trickiness, I would guess, is making sure that we never fall back to the system Boost header if something goes wrong (like, if a file was moved or renamed in the user-provided Boost)?  Is this possible to accomplish in a way without the chance of leaving the CI machine in a corrupt state for the next user?&lt;/p&gt;</comment>
                            <comment id="1380624" author="david.golden" created="Fri, 9 Sep 2016 16:35:30 +0000"  >&lt;p&gt;We had a user on Windows with problems on 1.57; 1.59 fixed the problem.  So I think our claimed minimum needs to move.&lt;/p&gt;</comment>
                            <comment id="1380388" author="acm" created="Fri, 9 Sep 2016 12:28:35 +0000"  >&lt;p&gt;This is going to be tricky, in practice, due to how boost gets installed. Note that we do require boost 1.56 as our current minimum.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                            <outwardlinks description="related to">
                                        <issuelink>
            <issuekey id="312976">CXX-1012</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="341334">CXX-1182</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </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_10857" key="com.pyxis.greenhopper.jira:gh-epic-link">
                        <customfieldname>Epic Link</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>CXX-1023</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hr6mo7:</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>