<!-- 
RSS generated by JIRA (1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d) at Thu Feb 08 23:22:40 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 add field=key&field=summary to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>FOLIO Jira</title>
    <link>https://folio-org.atlassian.net</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>1001.0.0-SNAPSHOT</version>
        <build-number>100246</build-number>
        <build-date>07-02-2024</build-date>
    </build-info>

<item>
            <title>[FOLIO-2708] Major/feature releases for quarterly FOLIO releases from master?</title>
                <link>https://folio-org.atlassian.net/browse/FOLIO-2708</link>
                <project id="10290" key="FOLIO">FOLIO</project>
                    <description>&lt;p&gt;Before Q2 2020 FOLIO had this policy for major/feature releases:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://dev.folio.org/guides/regular-releases/&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://dev.folio.org/guides/regular-releases/&lt;/a&gt; :&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;A typical strategy for a module development is to keep doing the normal work in feature branches and merging to master until its final release and cut-off date. &lt;/p&gt;&lt;/blockquote&gt;

&lt;blockquote&gt;&lt;p&gt;Hold off feature branches that are not to be included in the release.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;&lt;a href=&quot;https://dev.folio.org/guidelines/release-procedures/#summary-mvn&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://dev.folio.org/guidelines/release-procedures/#summary-mvn&lt;/a&gt; :&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;Merge temporary release branch tmp-release-X.Y.0 to master.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;This advocates feature releases from master (master branch may also be called main, mainline or default).&lt;/p&gt;

&lt;p&gt;This was changed for Q2 2020 (&lt;a href=&quot;https://folio-org.atlassian.net/browse/MODINVSTOR-536?focusedCommentId=130253&amp;amp;page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;MODINVSTOR-536 comment 82656&lt;/a&gt;):&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;Releasing to Q2 2020 or Q2 2020 Hotfix from master is not allowed. Team supposed to create Q2 2020 branch and commit changes to both master and Q2 2020 branch.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Task:&lt;br/&gt;
Tech leads and the members of the release group: Please approve or reject this change.&lt;br/&gt;
Then update &lt;a href=&quot;https://dev.folio.org/guidelines/release-procedures/#summary-mvn&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://dev.folio.org/guidelines/release-procedures/#summary-mvn&lt;/a&gt; accordingly.&lt;/p&gt;</description>
                <environment></environment>
        <key id="79681">FOLIO-2708</key>
            <summary>Major/feature releases for quarterly FOLIO releases from master?</summary>
                <type id="10003" iconUrl="https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium">Task</type>
                                            <priority id="10005" iconUrl="https://dev.folio.org/assets/jira-priority/tbd.svg">TBD</priority>
                        <status id="1" iconUrl="https://folio-org.atlassian.net/images/icons/statuses/open.png" description="The issue is open and ready for the assignee to start work on it.">Open</status>
                    <statusCategory id="2" key="new" colorName="blue-gray"/>
                                    <resolution id="-1">Unresolved</resolution>
                                                        <assignee accountid="-1">Unassigned</assignee>
                                                                <reporter accountid="5ee89462f7aa140abd82d11d">Julian Ladisch</reporter>
                                    <labels>
                            <label>devdoc</label>
                    </labels>
                <created>Wed, 29 Jul 2020 08:50:55 +0000</created>
                <updated>Thu, 29 Oct 2020 13:46:45 +0000</updated>
                                                                                <due></due>
                            <votes>0</votes>
                                    <watches>9</watches>
                                                                <comments>
                                                            <comment id="189523" author="5ee89462f7aa140abd82d11d" created="Wed, 29 Jul 2020 10:39:45 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5cffed1a5d548b0c51d6b19b&quot; class=&quot;user-hover&quot; rel=&quot;5cffed1a5d548b0c51d6b19b&quot; data-account-id=&quot;5cffed1a5d548b0c51d6b19b&quot; accountid=&quot;5cffed1a5d548b0c51d6b19b&quot; rel=&quot;noreferrer&quot;&gt;Anton Emelianov&lt;/a&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=63e2a2771b13d42998e4e706&quot; class=&quot;user-hover&quot; rel=&quot;63e2a2771b13d42998e4e706&quot; data-account-id=&quot;63e2a2771b13d42998e4e706&quot; accountid=&quot;63e2a2771b13d42998e4e706&quot; rel=&quot;noreferrer&quot;&gt;Marc Johnson&lt;/a&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5ed55244bc90a106063c7&quot; class=&quot;user-hover&quot; rel=&quot;5af5ed55244bc90a106063c7&quot; data-account-id=&quot;5af5ed55244bc90a106063c7&quot; accountid=&quot;5af5ed55244bc90a106063c7&quot; rel=&quot;noreferrer&quot;&gt;Cate Boerema&lt;/a&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ab8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; class=&quot;user-hover&quot; rel=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; data-account-id=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; accountid=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; rel=&quot;noreferrer&quot;&gt;Jakub Skoczen&lt;/a&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5b1434bffa615349cb01726d&quot; class=&quot;user-hover&quot; rel=&quot;5b1434bffa615349cb01726d&quot; data-account-id=&quot;5b1434bffa615349cb01726d&quot; accountid=&quot;5b1434bffa615349cb01726d&quot; rel=&quot;noreferrer&quot;&gt;Mark Veksler&lt;/a&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ae08bd47b44642d39d323c4&quot; class=&quot;user-hover&quot; rel=&quot;5ae08bd47b44642d39d323c4&quot; data-account-id=&quot;5ae08bd47b44642d39d323c4&quot; accountid=&quot;5ae08bd47b44642d39d323c4&quot; rel=&quot;noreferrer&quot;&gt;Mike Gorrell&lt;/a&gt; Can the tech leads and the members of the release group discuss and either approve or reject this change, and update the policy documentation accordingly?&lt;/p&gt;</comment>
                                                            <comment id="189524" author="5ee89462f7aa140abd82d11d" created="Wed, 29 Jul 2020 10:42:56 +0000"  >&lt;p&gt;I would like this change being rejected and reverted. Releasing from master is simpler, and it has lower risk because master is deployed to and tested on folio-testing.&lt;/p&gt;</comment>
                                                            <comment id="189526" author="5af5ed55244bc90a106063c7" created="Wed, 29 Jul 2020 11:01:57 +0000"  >&lt;blockquote&gt;&lt;p&gt;Releasing to Q2 2020 or Q2 2020 Hotfix from master is not allowed. Team supposed to create Q2 2020 branch and commit changes to both master and Q2 2020 branch.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Didn&apos;t &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5cffed1a5d548b0c51d6b19b&quot; class=&quot;user-hover&quot; rel=&quot;5cffed1a5d548b0c51d6b19b&quot; data-account-id=&quot;5cffed1a5d548b0c51d6b19b&quot; accountid=&quot;5cffed1a5d548b0c51d6b19b&quot; rel=&quot;noreferrer&quot;&gt;Anton Emelianov&lt;/a&gt; already walk back this statement?  See Slack discussion pasted into this comment: &lt;a href=&quot;https://folio-org.atlassian.net/browse/MODINVSTOR-536?focusedCommentId=130291&amp;amp;page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://folio-org.atlassian.net/browse/MODINVSTOR-536?focusedCommentId=130291&amp;amp;page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;My guess is that there was never really a Q2 policy change, just a comment left in haste which was subsequently reversed based on sensible input from others in 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;MODINVSTOR-536&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/MODINVSTOR-536&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Separate filtering from response generation in oai-pmh view &quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            MODINVSTOR-536
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
.  &lt;/p&gt;

&lt;p&gt;My feeling is that, to the extent possible, we should be making patch releases for hotfixes.  But, this can be much harder/riskier for backend modules than frontend ones and, given that, we should have the flexibility to release from master (a release branch that is identical to master) when the relevant tech leads think it&apos;s best (with approval from #release_bug_triage group).  This is the approach we have always taken, it has served us well and I don&apos;t see any reason to change.&lt;/p&gt;

&lt;p&gt;Let me know if I am not understanding.&lt;/p&gt;</comment>
                                                            <comment id="189528" author="63e2a2771b13d42998e4e706" created="Wed, 29 Jul 2020 11:21:14 +0000"  >&lt;blockquote&gt;&lt;p&gt;Didn&apos;t &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5cffed1a5d548b0c51d6b19b&quot; class=&quot;user-hover&quot; rel=&quot;5cffed1a5d548b0c51d6b19b&quot; data-account-id=&quot;5cffed1a5d548b0c51d6b19b&quot; accountid=&quot;5cffed1a5d548b0c51d6b19b&quot; rel=&quot;noreferrer&quot;&gt;Anton Emelianov&lt;/a&gt; already walk back this statement?&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;I don&apos;t think folks interpreted it that way, given the way the release was performed. &lt;/p&gt;

&lt;p&gt;The release yesterday was made in the non-standard way that &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ee89462f7aa140abd82d11d&quot; class=&quot;user-hover&quot; rel=&quot;5ee89462f7aa140abd82d11d&quot; data-account-id=&quot;5ee89462f7aa140abd82d11d&quot; accountid=&quot;5ee89462f7aa140abd82d11d&quot; rel=&quot;noreferrer&quot;&gt;Julian Ladisch&lt;/a&gt; suggested using a branch that had the same starting point as the mainline (however never rejoined mainline). I believe it was done that way in order to be compliant with &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5cffed1a5d548b0c51d6b19b&quot; class=&quot;user-hover&quot; rel=&quot;5cffed1a5d548b0c51d6b19b&quot; data-account-id=&quot;5cffed1a5d548b0c51d6b19b&quot; accountid=&quot;5cffed1a5d548b0c51d6b19b&quot; rel=&quot;noreferrer&quot;&gt;Anton Emelianov&lt;/a&gt;&apos;s statement. (&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5c925a60a5cb042c635a5b2e&quot; class=&quot;user-hover&quot; rel=&quot;5c925a60a5cb042c635a5b2e&quot; data-account-id=&quot;5c925a60a5cb042c635a5b2e&quot; accountid=&quot;5c925a60a5cb042c635a5b2e&quot; rel=&quot;noreferrer&quot;&gt;Anastasiia Zakharova&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=712020%3A16d6159e-38b2-4249-9b56-7780b9ca438e&quot; class=&quot;user-hover&quot; rel=&quot;712020:16d6159e-38b2-4249-9b56-7780b9ca438e&quot; data-account-id=&quot;712020:16d6159e-38b2-4249-9b56-7780b9ca438e&quot; accountid=&quot;712020:16d6159e-38b2-4249-9b56-7780b9ca438e&quot; rel=&quot;noreferrer&quot;&gt;Oleksandr Yatsenko&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ee89462f7aa140abd82d11d&quot; class=&quot;user-hover&quot; rel=&quot;5ee89462f7aa140abd82d11d&quot; data-account-id=&quot;5ee89462f7aa140abd82d11d&quot; accountid=&quot;5ee89462f7aa140abd82d11d&quot; rel=&quot;noreferrer&quot;&gt;Julian Ladisch&lt;/a&gt; please advise if my interpretation of your comments and our conversations is incorrect).&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;we should have the flexibility to release from master (a release branch that is identical to master)&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;My understanding of how the comments by &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5cffed1a5d548b0c51d6b19b&quot; class=&quot;user-hover&quot; rel=&quot;5cffed1a5d548b0c51d6b19b&quot; data-account-id=&quot;5cffed1a5d548b0c51d6b19b&quot; accountid=&quot;5cffed1a5d548b0c51d6b19b&quot; rel=&quot;noreferrer&quot;&gt;Anton Emelianov&lt;/a&gt; and &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ee89462f7aa140abd82d11d&quot; class=&quot;user-hover&quot; rel=&quot;5ee89462f7aa140abd82d11d&quot; data-account-id=&quot;5ee89462f7aa140abd82d11d&quot; accountid=&quot;5ee89462f7aa140abd82d11d&quot; rel=&quot;noreferrer&quot;&gt;Julian Ladisch&lt;/a&gt; have been interpreted is that a release from the mainline (in the sense that it follows our regular release procedure) and a release from a branch with an identical starting point to the mainline are considered different.&lt;/p&gt;

&lt;p&gt;I tried to express those differences in my follow up &lt;a href=&quot;https://folio-org.atlassian.net/browse/MODINVSTOR-536?focusedCommentId=130296&amp;amp;page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;comment&lt;/a&gt; on 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;MODINVSTOR-536&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/MODINVSTOR-536&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Separate filtering from response generation in oai-pmh view &quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            MODINVSTOR-536
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
. I get the sense that my explanation did not come across to folks.&lt;/p&gt;</comment>
                                                            <comment id="189531" author="615afd1cd9820f0070a09ef0" created="Fri, 31 Jul 2020 19:05:38 +0000"  >&lt;p&gt;It isn&apos;t clear to me that we will benefit from having strong rules/policy around what branches releases are tagged on. As &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ee89462f7aa140abd82d11d&quot; class=&quot;user-hover&quot; rel=&quot;5ee89462f7aa140abd82d11d&quot; data-account-id=&quot;5ee89462f7aa140abd82d11d&quot; accountid=&quot;5ee89462f7aa140abd82d11d&quot; rel=&quot;noreferrer&quot;&gt;Julian Ladisch&lt;/a&gt; noted, there is great appeal in releasing from master because it is deployed to the reference environments and enjoys widespread use, and therefore widespread manual testing. &lt;/p&gt;

&lt;p&gt;But mandating that we release only from master is, I think, impractical. As soon as we make a rule like that, we&apos;ll find we need to make an exception to it &amp;#8211; there are always exceptions; it is the way of things &amp;#8211; and then there will be much hand wringing about what to do, which could be avoided if we had just avoid the overly-strict policy in the first place. &lt;/p&gt;

&lt;p&gt;We continue to vigilantly pursue increased test coverage across all repositories. Hopefully, such automated testing will soon provide even better coverage than the de facto manual testing on the reference environments, and we&apos;ll feel confident about releasing from any branch where those tests pass. &lt;/p&gt;</comment>
                                                            <comment id="189534" author="5ee89462f7aa140abd82d11d" created="Fri, 31 Jul 2020 19:46:28 +0000"  >&lt;p&gt;This issue is not about mandating to release only from master.&lt;br/&gt;
This is not possible if the commits to be released and other commits not to be released are intermixed on master; this always requires a separate branch.&lt;br/&gt;
This issue is about allowing to release from master for the case that all commits on master are to be released.&lt;/p&gt;
</comment>
                                                            <comment id="189537" author="63e2a2771b13d42998e4e706" created="Wed, 14 Oct 2020 11:31:27 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5cffed1a5d548b0c51d6b19b&quot; class=&quot;user-hover&quot; rel=&quot;5cffed1a5d548b0c51d6b19b&quot; data-account-id=&quot;5cffed1a5d548b0c51d6b19b&quot; accountid=&quot;5cffed1a5d548b0c51d6b19b&quot; rel=&quot;noreferrer&quot;&gt;Anton Emelianov&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5cf6c546b87c300f36eb7b9a&quot; class=&quot;user-hover&quot; rel=&quot;5cf6c546b87c300f36eb7b9a&quot; data-account-id=&quot;5cf6c546b87c300f36eb7b9a&quot; accountid=&quot;5cf6c546b87c300f36eb7b9a&quot; rel=&quot;noreferrer&quot;&gt;Craig McNally&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ab8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; class=&quot;user-hover&quot; rel=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; data-account-id=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; accountid=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; rel=&quot;noreferrer&quot;&gt;Jakub Skoczen&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5ee89462f7aa140abd82d11d&quot; class=&quot;user-hover&quot; rel=&quot;5ee89462f7aa140abd82d11d&quot; data-account-id=&quot;5ee89462f7aa140abd82d11d&quot; accountid=&quot;5ee89462f7aa140abd82d11d&quot; rel=&quot;noreferrer&quot;&gt;Julian Ladisch&lt;/a&gt; &lt;/p&gt;

&lt;p&gt;I&apos;m resurrecting this topic as it has come upon again (see 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;CIRC-936&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/CIRC-936&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Release mod-circulation 19.1.0&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            CIRC-936
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
 for context) and I don&apos;t feel I have clear guidance to give.&lt;/p&gt;

&lt;p&gt;I&apos;m going to outline an example and ask for folks views on which approaches are acceptable.&lt;/p&gt;

&lt;h3&gt;&lt;a name=&quot;Situation&quot;&gt;&lt;/a&gt;Situation&lt;/h3&gt;

&lt;p&gt;The last release of a module is 5.3.0. &lt;/p&gt;

&lt;p&gt;There have been various changes to the mainline, lets call them A, B, C and D&lt;/p&gt;

&lt;h3&gt;&lt;a name=&quot;Goal&quot;&gt;&lt;/a&gt;Goal&lt;/h3&gt;

&lt;p&gt;To make a release containing new features B and D&lt;/p&gt;

&lt;h3&gt;&lt;a name=&quot;Options&quot;&gt;&lt;/a&gt;Options&lt;/h3&gt;

&lt;ol&gt;
	&lt;li&gt;Make a feature release (5.2.0) from the mainline.&lt;/li&gt;
	&lt;li&gt;Make a feature release (5.2.0) from a new long lived branch (b5.2, based upon the 5.1.0 release). Separate change needed on the mainline to move the next version to 5.3.0.&lt;/li&gt;
	&lt;li&gt;Make a feature release (5.2.0) from a new long lived branch (b5.2, based upon the latest revision of the mainline that is appropriate, after the v5.1.0 release). Separate change needed on the mainline to move the next version to 5.3.0.&lt;/li&gt;
	&lt;li&gt;Make a bug fix release (5.1.1) from a long lived branch (b5.1) based upon the 5.1.0 release. This would disguise the new features as a bug fix.&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;The release from option 1 would also include other changes A and C. The releases from options 2, 3 and 4 would only includes changes B and D (usually caveats about cherry picking / merges still apply).&lt;/p&gt;

&lt;h3&gt;&lt;a name=&quot;Questions&quot;&gt;&lt;/a&gt;Questions&lt;/h3&gt;

&lt;p&gt;Which of these options are acceptable choices for a lead maintainer / developer to make?&lt;/p&gt;

&lt;p&gt;If folks consider option 1 to be unacceptable in the above example, would it be acceptable if the only changes on the mainline were B and D?&lt;/p&gt;

&lt;p&gt;cc: &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=999854%3A4c90e51c-83a3-4c35-a09e-eafd9949308b&quot; class=&quot;user-hover&quot; rel=&quot;999854:4c90e51c-83a3-4c35-a09e-eafd9949308b&quot; data-account-id=&quot;999854:4c90e51c-83a3-4c35-a09e-eafd9949308b&quot; accountid=&quot;999854:4c90e51c-83a3-4c35-a09e-eafd9949308b&quot; rel=&quot;noreferrer&quot;&gt;Former user&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=63519767d66d8108a1226c09&quot; class=&quot;user-hover&quot; rel=&quot;63519767d66d8108a1226c09&quot; data-account-id=&quot;63519767d66d8108a1226c09&quot; accountid=&quot;63519767d66d8108a1226c09&quot; rel=&quot;noreferrer&quot;&gt;Viachaslau Khandramai&lt;/a&gt;&lt;/p&gt;</comment>
                                                            <comment id="189539" author="5cf6c546b87c300f36eb7b9a" created="Thu, 29 Oct 2020 13:46:45 +0000"  >&lt;p&gt;This is my take on this... I&apos;d love to hear other&apos;s opinions though&lt;/p&gt;

&lt;p&gt;I think it depends on if features A and C include breaking compatibility changes, doesn&apos;t it?  &lt;/p&gt;

&lt;p&gt;Assuming that there&apos;s a reason to NOT include A and C in this release, I personally would go with option 2 unless option 3 didn&apos;t require cherry picking - that is there&apos;s a revision of mainline which has the features you want and doesn&apos;t have the features you don&apos;t want.&lt;/p&gt;

&lt;p&gt;I would stay away from option 4.  Disguising features as bugs is unacceptable IMO.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="81640">FOLIO-2538</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10000" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummarycf">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10019" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i01hmj:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10020" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10024" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>[CHART] Date of First Response</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Wed, 29 Jul 2020 11:01:57 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                </customfields>
    </item>
</channel>
</rss>