You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@solr.apache.org by Houston Putman <ho...@apache.org> on 2023/07/07 17:21:23 UTC
New branch and feature freeze for Solr 9.3.0
NOTICE:
Branch branch_9_3 has been cut and versions updated to 9.4 on stable branch.
Please observe the normal rules:
* No new features may be committed to the branch.
* Documentation patches, build patches and serious bug fixes may be
committed to the branch. However, you should submit all patches you
want to commit to Jira first to give others the chance to review
and possibly vote against the patch. Keep in mind that it is our
main intention to keep the branch as stable as possible.
* All patches that are intended for the branch should first be committed
to the unstable branch, merged into the stable branch, and then into
the current release branch.
* Normal unstable and stable branch development may continue as usual.
However, if you plan to commit a big change to the unstable branch
while the branch feature freeze is in effect, think twice: can't the
addition wait a couple more days? Merges of bug fixes into the branch
may become more difficult.
* Only Jira issues with Fix version 9.3 and priority "Blocker" will delay
a release candidate build.
Re: New branch and feature freeze for Solr 9.3.0
Posted by Houston Putman <ho...@apache.org>.
Ok thanks everyone, I will cut the RC now.
- Houston
On Thu, Jul 13, 2023 at 3:25 AM Alessandro Benedetti <a....@sease.io>
wrote:
> Thanks for coordinating the release Houston, from my side all has been
> done!
> I asked Elia(my colleague) to monitor the builds after the cherry picks,
> and I heard no complaints!
>
> Cheers
> --------------------------
> *Alessandro Benedetti*
> Director @ Sease Ltd.
> *Apache Lucene/Solr Committer*
> *Apache Solr PMC Member*
>
> e-mail: a.benedetti@sease.io
>
>
> *Sease* - Information Retrieval Applied
> Consulting | Training | Open Source
>
> Website: Sease.io <http://sease.io/>
> LinkedIn <https://linkedin.com/company/sease-ltd> | Twitter
> <https://twitter.com/seaseltd> | Youtube
> <https://www.youtube.com/channel/UCDx86ZKLYNpI3gzMercM7BQ> | Github
> <https://github.com/seaseltd>
>
> [image: Mailtrack]
> <
> https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality11&
> >
> Sender
> notified by
> Mailtrack
> <
> https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality11&
> >
> 13/07/23,
> 09:23:30
>
> On Wed, 12 Jul 2023 at 17:23, Houston Putman <ho...@apache.org> wrote:
>
> > Thanks for the update David, and for cleaning that up.
> >
> > We are waiting on a ticket that needs a review, and I'm getting the other
> > stuff merged in the meantime.
> >
> > I'm planning on adding another ticket for the 9.3 release: SOLR-16856
> > <https://issues.apache.org/jira/browse/SOLR-16856> but that should be
> > reviewed and ready later today.
> >
> > - Houston
> >
> > On Tue, Jul 11, 2023 at 6:39 PM David Smiley <da...@gmail.com>
> > wrote:
> >
> > > https://issues.apache.org/jira/browse/SOLR-16507 is a bit unusual;
> there
> > > are two changes/PRs by different people somewhat related with only one
> of
> > > them backported to 9x; the other was forgotten (my bad). Changes.txt
> > entry
> > > for main branch shows this under 9.3 but hasn't been ported yet. I
> > intend
> > > to fix this now; back-port to 9x and branch_9_3
> > > https://github.com/apache/solr/pull/1775
> > > I'll then resolve the JIRA issue against 9.3.
> > >
> > > ~ David
> > >
> > >
> > > On Fri, Jul 7, 2023 at 2:05 PM Houston Putman <ho...@apache.org>
> > wrote:
> > >
> > > > Please update the draft release notes if you have any suggestions:
> > > >
> > > > https://cwiki.apache.org/confluence/display/SOLR/ReleaseNote9_3_0
> > > >
> > > > - Houston
> > > >
> > > > On Fri, Jul 7, 2023 at 1:23 PM Houston Putman <ho...@apache.org>
> > > wrote:
> > > >
> > > > > Currently there are three tickets that I have added as blockers:
> (All
> > > > > should be merged by Monday, when I plan to cut an RC)
> > > > >
> > > > > - SOLR-16675 <https://issues.apache.org/jira/browse/SOLR-16675>
> > > > > - SOLR-16878 <https://issues.apache.org/jira/browse/SOLR-16878>
> > > > > - SOLR-16877 <https://issues.apache.org/jira/browse/SOLR-16877>
> > > > >
> > > > > I also have 1 small PR that I plan to backport as well:
> > > > > https://github.com/apache/solr/pull/1766
> > > > >
> > > > > Please comment here before backporting to branch_9_3.
> > > > >
> > > > > - Houston
> > > > >
> > > > > On Fri, Jul 7, 2023 at 1:21 PM Houston Putman <ho...@apache.org>
> > > > wrote:
> > > > >
> > > > >> NOTICE:
> > > > >>
> > > > >> Branch branch_9_3 has been cut and versions updated to 9.4 on
> stable
> > > > >> branch.
> > > > >>
> > > > >> Please observe the normal rules:
> > > > >>
> > > > >> * No new features may be committed to the branch.
> > > > >> * Documentation patches, build patches and serious bug fixes may
> be
> > > > >> committed to the branch. However, you should submit all patches
> > you
> > > > >> want to commit to Jira first to give others the chance to review
> > > > >> and possibly vote against the patch. Keep in mind that it is our
> > > > >> main intention to keep the branch as stable as possible.
> > > > >> * All patches that are intended for the branch should first be
> > > committed
> > > > >> to the unstable branch, merged into the stable branch, and then
> > into
> > > > >> the current release branch.
> > > > >> * Normal unstable and stable branch development may continue as
> > usual.
> > > > >> However, if you plan to commit a big change to the unstable
> branch
> > > > >> while the branch feature freeze is in effect, think twice: can't
> > the
> > > > >> addition wait a couple more days? Merges of bug fixes into the
> > > branch
> > > > >> may become more difficult.
> > > > >> * Only Jira issues with Fix version 9.3 and priority "Blocker"
> will
> > > > delay
> > > > >> a release candidate build.
> > > > >>
> > > > >
> > > >
> > >
> >
>
Re: New branch and feature freeze for Solr 9.3.0
Posted by Alessandro Benedetti <a....@sease.io>.
Thanks for coordinating the release Houston, from my side all has been done!
I asked Elia(my colleague) to monitor the builds after the cherry picks,
and I heard no complaints!
Cheers
--------------------------
*Alessandro Benedetti*
Director @ Sease Ltd.
*Apache Lucene/Solr Committer*
*Apache Solr PMC Member*
e-mail: a.benedetti@sease.io
*Sease* - Information Retrieval Applied
Consulting | Training | Open Source
Website: Sease.io <http://sease.io/>
LinkedIn <https://linkedin.com/company/sease-ltd> | Twitter
<https://twitter.com/seaseltd> | Youtube
<https://www.youtube.com/channel/UCDx86ZKLYNpI3gzMercM7BQ> | Github
<https://github.com/seaseltd>
[image: Mailtrack]
<https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality11&>
Sender
notified by
Mailtrack
<https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality11&>
13/07/23,
09:23:30
On Wed, 12 Jul 2023 at 17:23, Houston Putman <ho...@apache.org> wrote:
> Thanks for the update David, and for cleaning that up.
>
> We are waiting on a ticket that needs a review, and I'm getting the other
> stuff merged in the meantime.
>
> I'm planning on adding another ticket for the 9.3 release: SOLR-16856
> <https://issues.apache.org/jira/browse/SOLR-16856> but that should be
> reviewed and ready later today.
>
> - Houston
>
> On Tue, Jul 11, 2023 at 6:39 PM David Smiley <da...@gmail.com>
> wrote:
>
> > https://issues.apache.org/jira/browse/SOLR-16507 is a bit unusual; there
> > are two changes/PRs by different people somewhat related with only one of
> > them backported to 9x; the other was forgotten (my bad). Changes.txt
> entry
> > for main branch shows this under 9.3 but hasn't been ported yet. I
> intend
> > to fix this now; back-port to 9x and branch_9_3
> > https://github.com/apache/solr/pull/1775
> > I'll then resolve the JIRA issue against 9.3.
> >
> > ~ David
> >
> >
> > On Fri, Jul 7, 2023 at 2:05 PM Houston Putman <ho...@apache.org>
> wrote:
> >
> > > Please update the draft release notes if you have any suggestions:
> > >
> > > https://cwiki.apache.org/confluence/display/SOLR/ReleaseNote9_3_0
> > >
> > > - Houston
> > >
> > > On Fri, Jul 7, 2023 at 1:23 PM Houston Putman <ho...@apache.org>
> > wrote:
> > >
> > > > Currently there are three tickets that I have added as blockers: (All
> > > > should be merged by Monday, when I plan to cut an RC)
> > > >
> > > > - SOLR-16675 <https://issues.apache.org/jira/browse/SOLR-16675>
> > > > - SOLR-16878 <https://issues.apache.org/jira/browse/SOLR-16878>
> > > > - SOLR-16877 <https://issues.apache.org/jira/browse/SOLR-16877>
> > > >
> > > > I also have 1 small PR that I plan to backport as well:
> > > > https://github.com/apache/solr/pull/1766
> > > >
> > > > Please comment here before backporting to branch_9_3.
> > > >
> > > > - Houston
> > > >
> > > > On Fri, Jul 7, 2023 at 1:21 PM Houston Putman <ho...@apache.org>
> > > wrote:
> > > >
> > > >> NOTICE:
> > > >>
> > > >> Branch branch_9_3 has been cut and versions updated to 9.4 on stable
> > > >> branch.
> > > >>
> > > >> Please observe the normal rules:
> > > >>
> > > >> * No new features may be committed to the branch.
> > > >> * Documentation patches, build patches and serious bug fixes may be
> > > >> committed to the branch. However, you should submit all patches
> you
> > > >> want to commit to Jira first to give others the chance to review
> > > >> and possibly vote against the patch. Keep in mind that it is our
> > > >> main intention to keep the branch as stable as possible.
> > > >> * All patches that are intended for the branch should first be
> > committed
> > > >> to the unstable branch, merged into the stable branch, and then
> into
> > > >> the current release branch.
> > > >> * Normal unstable and stable branch development may continue as
> usual.
> > > >> However, if you plan to commit a big change to the unstable branch
> > > >> while the branch feature freeze is in effect, think twice: can't
> the
> > > >> addition wait a couple more days? Merges of bug fixes into the
> > branch
> > > >> may become more difficult.
> > > >> * Only Jira issues with Fix version 9.3 and priority "Blocker" will
> > > delay
> > > >> a release candidate build.
> > > >>
> > > >
> > >
> >
>
Re: New branch and feature freeze for Solr 9.3.0
Posted by Houston Putman <ho...@apache.org>.
Thanks for the update David, and for cleaning that up.
We are waiting on a ticket that needs a review, and I'm getting the other
stuff merged in the meantime.
I'm planning on adding another ticket for the 9.3 release: SOLR-16856
<https://issues.apache.org/jira/browse/SOLR-16856> but that should be
reviewed and ready later today.
- Houston
On Tue, Jul 11, 2023 at 6:39 PM David Smiley <da...@gmail.com>
wrote:
> https://issues.apache.org/jira/browse/SOLR-16507 is a bit unusual; there
> are two changes/PRs by different people somewhat related with only one of
> them backported to 9x; the other was forgotten (my bad). Changes.txt entry
> for main branch shows this under 9.3 but hasn't been ported yet. I intend
> to fix this now; back-port to 9x and branch_9_3
> https://github.com/apache/solr/pull/1775
> I'll then resolve the JIRA issue against 9.3.
>
> ~ David
>
>
> On Fri, Jul 7, 2023 at 2:05 PM Houston Putman <ho...@apache.org> wrote:
>
> > Please update the draft release notes if you have any suggestions:
> >
> > https://cwiki.apache.org/confluence/display/SOLR/ReleaseNote9_3_0
> >
> > - Houston
> >
> > On Fri, Jul 7, 2023 at 1:23 PM Houston Putman <ho...@apache.org>
> wrote:
> >
> > > Currently there are three tickets that I have added as blockers: (All
> > > should be merged by Monday, when I plan to cut an RC)
> > >
> > > - SOLR-16675 <https://issues.apache.org/jira/browse/SOLR-16675>
> > > - SOLR-16878 <https://issues.apache.org/jira/browse/SOLR-16878>
> > > - SOLR-16877 <https://issues.apache.org/jira/browse/SOLR-16877>
> > >
> > > I also have 1 small PR that I plan to backport as well:
> > > https://github.com/apache/solr/pull/1766
> > >
> > > Please comment here before backporting to branch_9_3.
> > >
> > > - Houston
> > >
> > > On Fri, Jul 7, 2023 at 1:21 PM Houston Putman <ho...@apache.org>
> > wrote:
> > >
> > >> NOTICE:
> > >>
> > >> Branch branch_9_3 has been cut and versions updated to 9.4 on stable
> > >> branch.
> > >>
> > >> Please observe the normal rules:
> > >>
> > >> * No new features may be committed to the branch.
> > >> * Documentation patches, build patches and serious bug fixes may be
> > >> committed to the branch. However, you should submit all patches you
> > >> want to commit to Jira first to give others the chance to review
> > >> and possibly vote against the patch. Keep in mind that it is our
> > >> main intention to keep the branch as stable as possible.
> > >> * All patches that are intended for the branch should first be
> committed
> > >> to the unstable branch, merged into the stable branch, and then into
> > >> the current release branch.
> > >> * Normal unstable and stable branch development may continue as usual.
> > >> However, if you plan to commit a big change to the unstable branch
> > >> while the branch feature freeze is in effect, think twice: can't the
> > >> addition wait a couple more days? Merges of bug fixes into the
> branch
> > >> may become more difficult.
> > >> * Only Jira issues with Fix version 9.3 and priority "Blocker" will
> > delay
> > >> a release candidate build.
> > >>
> > >
> >
>
Re: New branch and feature freeze for Solr 9.3.0
Posted by David Smiley <da...@gmail.com>.
https://issues.apache.org/jira/browse/SOLR-16507 is a bit unusual; there
are two changes/PRs by different people somewhat related with only one of
them backported to 9x; the other was forgotten (my bad). Changes.txt entry
for main branch shows this under 9.3 but hasn't been ported yet. I intend
to fix this now; back-port to 9x and branch_9_3
https://github.com/apache/solr/pull/1775
I'll then resolve the JIRA issue against 9.3.
~ David
On Fri, Jul 7, 2023 at 2:05 PM Houston Putman <ho...@apache.org> wrote:
> Please update the draft release notes if you have any suggestions:
>
> https://cwiki.apache.org/confluence/display/SOLR/ReleaseNote9_3_0
>
> - Houston
>
> On Fri, Jul 7, 2023 at 1:23 PM Houston Putman <ho...@apache.org> wrote:
>
> > Currently there are three tickets that I have added as blockers: (All
> > should be merged by Monday, when I plan to cut an RC)
> >
> > - SOLR-16675 <https://issues.apache.org/jira/browse/SOLR-16675>
> > - SOLR-16878 <https://issues.apache.org/jira/browse/SOLR-16878>
> > - SOLR-16877 <https://issues.apache.org/jira/browse/SOLR-16877>
> >
> > I also have 1 small PR that I plan to backport as well:
> > https://github.com/apache/solr/pull/1766
> >
> > Please comment here before backporting to branch_9_3.
> >
> > - Houston
> >
> > On Fri, Jul 7, 2023 at 1:21 PM Houston Putman <ho...@apache.org>
> wrote:
> >
> >> NOTICE:
> >>
> >> Branch branch_9_3 has been cut and versions updated to 9.4 on stable
> >> branch.
> >>
> >> Please observe the normal rules:
> >>
> >> * No new features may be committed to the branch.
> >> * Documentation patches, build patches and serious bug fixes may be
> >> committed to the branch. However, you should submit all patches you
> >> want to commit to Jira first to give others the chance to review
> >> and possibly vote against the patch. Keep in mind that it is our
> >> main intention to keep the branch as stable as possible.
> >> * All patches that are intended for the branch should first be committed
> >> to the unstable branch, merged into the stable branch, and then into
> >> the current release branch.
> >> * Normal unstable and stable branch development may continue as usual.
> >> However, if you plan to commit a big change to the unstable branch
> >> while the branch feature freeze is in effect, think twice: can't the
> >> addition wait a couple more days? Merges of bug fixes into the branch
> >> may become more difficult.
> >> * Only Jira issues with Fix version 9.3 and priority "Blocker" will
> delay
> >> a release candidate build.
> >>
> >
>
Re: New branch and feature freeze for Solr 9.3.0
Posted by Houston Putman <ho...@apache.org>.
Please update the draft release notes if you have any suggestions:
https://cwiki.apache.org/confluence/display/SOLR/ReleaseNote9_3_0
- Houston
On Fri, Jul 7, 2023 at 1:23 PM Houston Putman <ho...@apache.org> wrote:
> Currently there are three tickets that I have added as blockers: (All
> should be merged by Monday, when I plan to cut an RC)
>
> - SOLR-16675 <https://issues.apache.org/jira/browse/SOLR-16675>
> - SOLR-16878 <https://issues.apache.org/jira/browse/SOLR-16878>
> - SOLR-16877 <https://issues.apache.org/jira/browse/SOLR-16877>
>
> I also have 1 small PR that I plan to backport as well:
> https://github.com/apache/solr/pull/1766
>
> Please comment here before backporting to branch_9_3.
>
> - Houston
>
> On Fri, Jul 7, 2023 at 1:21 PM Houston Putman <ho...@apache.org> wrote:
>
>> NOTICE:
>>
>> Branch branch_9_3 has been cut and versions updated to 9.4 on stable
>> branch.
>>
>> Please observe the normal rules:
>>
>> * No new features may be committed to the branch.
>> * Documentation patches, build patches and serious bug fixes may be
>> committed to the branch. However, you should submit all patches you
>> want to commit to Jira first to give others the chance to review
>> and possibly vote against the patch. Keep in mind that it is our
>> main intention to keep the branch as stable as possible.
>> * All patches that are intended for the branch should first be committed
>> to the unstable branch, merged into the stable branch, and then into
>> the current release branch.
>> * Normal unstable and stable branch development may continue as usual.
>> However, if you plan to commit a big change to the unstable branch
>> while the branch feature freeze is in effect, think twice: can't the
>> addition wait a couple more days? Merges of bug fixes into the branch
>> may become more difficult.
>> * Only Jira issues with Fix version 9.3 and priority "Blocker" will delay
>> a release candidate build.
>>
>
Re: New branch and feature freeze for Solr 9.3.0
Posted by Houston Putman <ho...@apache.org>.
Currently there are three tickets that I have added as blockers: (All
should be merged by Monday, when I plan to cut an RC)
- SOLR-16675 <https://issues.apache.org/jira/browse/SOLR-16675>
- SOLR-16878 <https://issues.apache.org/jira/browse/SOLR-16878>
- SOLR-16877 <https://issues.apache.org/jira/browse/SOLR-16877>
I also have 1 small PR that I plan to backport as well:
https://github.com/apache/solr/pull/1766
Please comment here before backporting to branch_9_3.
- Houston
On Fri, Jul 7, 2023 at 1:21 PM Houston Putman <ho...@apache.org> wrote:
> NOTICE:
>
> Branch branch_9_3 has been cut and versions updated to 9.4 on stable
> branch.
>
> Please observe the normal rules:
>
> * No new features may be committed to the branch.
> * Documentation patches, build patches and serious bug fixes may be
> committed to the branch. However, you should submit all patches you
> want to commit to Jira first to give others the chance to review
> and possibly vote against the patch. Keep in mind that it is our
> main intention to keep the branch as stable as possible.
> * All patches that are intended for the branch should first be committed
> to the unstable branch, merged into the stable branch, and then into
> the current release branch.
> * Normal unstable and stable branch development may continue as usual.
> However, if you plan to commit a big change to the unstable branch
> while the branch feature freeze is in effect, think twice: can't the
> addition wait a couple more days? Merges of bug fixes into the branch
> may become more difficult.
> * Only Jira issues with Fix version 9.3 and priority "Blocker" will delay
> a release candidate build.
>