<!-- 
RSS generated by JIRA (5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9) at Sun May 26 00:48:10 CDT 2013

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 add field=key&field=summary to the URL of your request.
For example:
http://www.couchbase.com/issues/si/jira.issueviews:issue-xml/MB-3333/MB-3333.xml?field=key&field=summary
-->
<rss version="0.92" >
<channel>
    <title>Couchbase</title>
    <link>http://www.couchbase.com/issues</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>5.2.4</version>
        <build-number>845</build-number>
        <build-date>26-12-2012</build-date>
    </build-info>

<item>
            <title>[MB-3333] Document that network filesystems are unsupported</title>
                <link>http://www.couchbase.com/issues/browse/MB-3333</link>
                <project id="10010" key="MB">Couchbase Server</project>
                        <description>When reading about the details of WAL, it&amp;#39;s noted that it is not supported on either CIFS or NFS filesystems.  Block based network storage (iSCSI, EBS, etc.) should be fine, but NFS and CIFS are not supported.</description>
                <environment></environment>
            <key id="13434">MB-3333</key>
            <summary>Document that network filesystems are unsupported</summary>
                <type id="1" iconUrl="http://www.couchbase.com/issues/images/icons/issuetypes/bug.png">Bug</type>
                                <priority id="1" iconUrl="http://www.couchbase.com/issues/images/icons/priorities/blocker.png">Blocker</priority>
                    <status id="5" iconUrl="http://www.couchbase.com/issues/images/icons/statuses/resolved.png">Resolved</status>
                    <resolution id="1">Fixed</resolution>
                    <security id="10011">Public</security>
                        <assignee username="mccouch">MC Brown</assignee>
                                <reporter username="ingenthr">Matt Ingenthron</reporter>
                        <labels>
                        <label>1.6.4-release-notes</label>
                        <label>1.6.5.3-release-notes</label>
                        <label>1.7.0-release-notes</label>
                        <label>1.7.1-release-notes</label>
                    </labels>
                <created>Sat, 15 Jan 2011 19:14:45 -0600</created>
                <updated>Wed, 28 Mar 2012 00:58:39 -0500</updated>
                    <resolved>Wed, 28 Mar 2012 00:58:39 -0500</resolved>
                            <version>1.6.4</version>
                <version>1.6.4.1</version>
                <version>1.6.5</version>
                                <fixVersion>1.7.1</fixVersion>
                                <component>documentation</component>
                                <votes>0</votes>
                        <watches>0</watches>
                                                    <comments>
                    <comment id="21345" author="farshid" created="Sun, 10 Jul 2011 13:50:04 -0500"  >i think this is already part of the release notes and we dont need to keep the bug open to remember it as release notes.&lt;br/&gt;
we are using tags to create the list</comment>
                    <comment id="25217" author="ingenthr" created="Tue, 27 Mar 2012 15:43:55 -0500"  >But this is part of system requirements, not a release note.  Reopening.  Limitations we expect to always have should not live in release notes.</comment>
                    <comment id="25245" author="mccouch" created="Wed, 28 Mar 2012 00:58:39 -0500"  >I&amp;#39;ve added this requirement to the list of requirements in the installation section in all the manuals. </comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
                <customfields>
                                                                        <customfield id="customfield_10180" key="com.atlassian.jira.ext.charting:firstresponsedate">
                <customfieldname>Date of First Response</customfieldname>
                <customfieldvalues>
                    <customfieldvalue>Sun, 10 Jul 2011 13:50:04 -0500</customfieldvalue>

                </customfieldvalues>
            </customfield>
                                                                                    <customfield id="customfield_10010" key="com.atlassian.jira.plugin.system.customfieldtypes:multicheckboxes">
                <customfieldname>Flagged</customfieldname>
                <customfieldvalues>
                        <customfieldvalue key="10010"><![CDATA[Release Note]]></customfieldvalue>
    
                </customfieldvalues>
            </customfield>
                                                                                                                                                <customfield id="customfield_10081" key="com.pyxis.greenhopper.jira:gh-global-rank">
                <customfieldname>Rank</customfieldname>
                <customfieldvalues>
                    <customfieldvalue>1830</customfieldvalue>
                </customfieldvalues>
            </customfield>
                                                                                                                                                                                        <customfield id="customfield_10181" key="com.atlassian.jira.ext.charting:timeinstatus">
                <customfieldname>Time In Status</customfieldname>
                <customfieldvalues>
                    
                </customfieldvalues>
            </customfield>
                                                </customfields>
    </item>
</channel>
</rss>