Indeed that fixed it. Thanks Cassandra!

On Thu, Jul 11, 2019 at 3:33 PM Cassandra Targett <[email protected]>
wrote:

> I fixed it, I think - you needed to be added to the PMC group for the
> LUCENE project. Please try it again.
>
> Cassandra
> On Jul 11, 2019, 6:21 AM -0500, Ignacio Vera <[email protected]>, wrote:
>
> In addition I could add a new Jira version for Solr:
>
> -
> https://issues.apache.org/jira/plugins/servlet/project-config/SOLR/versions
>
>
> But it seems I do not have privileges for Lucene:
>
>
> -
> https://issues.apache.org/jira/plugins/servlet/project-config/LUCENE/versions
>
> On Thu, Jul 11, 2019 at 1:04 PM Ignacio Vera <[email protected]> wrote:
>
> Hi,
>
> The branch has been created, As a reminder, this branch is on feature
> freeze and only documentation or build patches should be committed. I will
> be waiting for LUCENE-8907 to start building the first release candidate.
> Let me know if there is any other blocker before we can start the release
> process.
>
> It seems I do not have the permissions to create the Jenkins jobs for this
> branch, maybe Steve can help here?
>
> Thanks,
>
> Ignacio
>
> On Thu, Jul 11, 2019 at 4:51 AM David Smiley <[email protected]>
> wrote:
>
> BTW for 8.2.0 I updated Solr's CHANGES.txt to split out issues that seemed
> to be Improvements that were not really New Features.
>
> ~ David Smiley
> Apache Lucene/Solr Search Developer
> http://www.linkedin.com/in/davidwsmiley
>
>
> On Wed, Jul 10, 2019 at 10:38 AM Ignacio Vera <[email protected]> wrote:
>
> Thanks Tomoko for taking care of that.
>
> On Wed, Jul 10, 2019 at 4:03 PM Đạt Cao Mạnh <[email protected]>
> wrote:
>
> Hi Ignacio,
>
> 8.1.2 bugfix release will cancelled. You can go ahead with 8.2 release.
>
> Thanks!
>
> On Wed, 10 Jul 2019 at 20:38, Tomoko Uchida <[email protected]>
> wrote:
>
> Hi,
> I opened a blocker issue a while ago for release 8.2:
> https://issues.apache.org/jira/browse/LUCENE-8907
>
> Sorry about that, I noticed the backwards incompatibility we have to
> deal with today. If there are no objections, I will revert the all
> related commits from the branch_8x and 8_2 in a few days.
>
> Thanks,
> Tomoko
>
> 2019年7月10日(水) 22:02 Ignacio Vera <[email protected]>:
> >
> > Hi,
> >
> > All the issues listed above has been already committed and I see no
> blockers for release 8.2. I will cut the branch tomorrow around 10am CEST
> and I will wait for the decision on the bug release 8.1.2 to schedule the
> build of the first release candidate. Please let us know if this is
> troublesome for you.
> >
> > Thanks,
> >
> > Ignacio
> >
> >
> > On Tue, Jul 2, 2019 at 2:59 AM Joel Bernstein <[email protected]>
> wrote:
> >>
> >> I've got one issue that I'd like to get in (
> https://issues.apache.org/jira/browse/SOLR-13589), which I should have
> wrapped up in a day or two. +1 for around July 10th.
> >>
> >> On Mon, Jul 1, 2019 at 5:14 PM Nicholas Knize <[email protected]> wrote:
> >>>
> >>> +1 for starting the 8.2 release process. I think it would be good to
> get the LUCENE-8632 feature into 8.2 along with the BKD improvements and
> changes in LUCENE-8888 and LUCENE-8896
> >>>
> >>> Nicholas Knize, Ph.D., GISP
> >>> Geospatial Software Guy  |  Elasticsearch
> >>> Apache Lucene PMC Member and Committer
> >>> [email protected]
> >>>
> >>>
> >>> On Wed, Jun 26, 2019 at 9:34 AM Ignacio Vera <[email protected]>
> wrote:
> >>>>
> >>>> Hi all,
> >>>>
> >>>> 8.1 has been released on May 16th and we have new features,
> enhancements and fixes that are not released yet so I'd like to start
> thinking in releasing Lucene/Solr 8.2.0.
> >>>>
> >>>> I can create the 8.2 branch in two weeks time (around July 10th) and
> build the first RC by the end of that week if that works for everyone.
> Please let me know if there are bug fixes that needs to be fixed in 8.2 and
> might not be ready by then.
> >>>>
> >>>> Cheers,
> >>>>
> >>>> Ignacio
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
> --
> *Best regards,*
> *Cao Mạnh Đạt*
> *E-mail: [email protected] <[email protected]>*
>
>

Reply via email to