PS: Thank you everyone who involved in voting and testing the release.

On Wed, May 22, 2019 at 1:17 PM Kevin Ratnasekera <djkevincr1...@gmail.com>
wrote:

> Hi all,
>
> I’m hereby call off the vote for RC1 due to some issues while tests are
> carried out. We will address [1] and [2] with the RC2.
>
> [1] https://issues.apache.org/jira/browse/GORA-615
> [2] https://issues.apache.org/jira/browse/GORA-616
>
> Regards
> Kevin
>
> On Tue, May 21, 2019 at 4:34 PM Sheriffo Ceesay <sneceesa...@gmail.com>
> wrote:
>
>> I am currently testing the 0.9 release using the gora-tutorial module. The
>> error below is thrown which leads to no output from the LogManager.
>>
>> bin/gora logmanager -parse gora-tutorial/src/main/resources/access.log
>>
>> SLF4J: Class path contains multiple SLF4J bindings.
>> SLF4J: Found binding in
>>
>> [jar:file:/home/user/apache-gora-0.9/gora-tutorial/lib/log4j-slf4j-impl-2.11.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
>> SLF4J: Found binding in
>>
>> [jar:file:/home/user/apache-gora-0.9/gora-tutorial/lib/slf4j-log4j12-1.6.6.jar!/org/slf4j/impl/StaticLoggerBinder.class]
>> SLF4J: Found binding in
>>
>> [jar:file:/home/user/apache-gora-0.9/gora-tutorial/lib/slf4j-simple-1.6.6.jar!/org/slf4j/impl/StaticLoggerBinder.class]
>> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
>> explanation.
>> SLF4J: Actual binding is of type
>> [org.apache.logging.slf4j.Log4jLoggerFactory]
>> ERROR StatusLogger No Log4j 2 configuration file found. Using default
>> configuration (logging only errors to the console), or user
>> programmatically provided configurations. Set system property
>> 'log4j2.debug' to show Log4j 2 internal initialization logging. See
>> https://logging.apache.org/log4j/2.x/manual/configuration.html for
>> instructions on how to configure Log4j 2
>>
>> Kevin and I are currently investigating this.
>>
>>
>> Thank you.
>>
>>
>>
>> **Sheriffo Ceesay**
>>
>>
>> On Tue, May 21, 2019 at 2:38 AM carlos muñoz <carlosr...@gmail.com>
>> wrote:
>>
>> > +1 Release this package as Apache Gora 0.9
>> >
>> > Regards,
>> > Carlos
>> >
>> > El vie., 10 may. 2019 a las 11:46, Madhawa Kasun Gunasekara (<
>> > madhaw...@gmail.com>) escribió:
>> >
>> > >  +1 Release this package as Apache Gora 0.9
>> > >
>> > > Tested Cassandra and Solr module.
>> > >
>> > > Thanks,
>> > > Madhawa
>> > >
>> > >
>> > > On Wed, May 8, 2019 at 11:59 AM Kevin Ratnasekera <
>> > djkevincr1...@gmail.com
>> > > >
>> > > wrote:
>> > >
>> > > > Hi all,
>> > > >
>> > > > This is the vote on first release candidate (RC01) for next Apache
>> > > >
>> > > > Gora release version 0.9.
>> > > >
>> > > > The VOTE will remain open for at least 72 hours.
>> > > >
>> > > > [ ] +1 Release this package as Apache Gora 0.9 ...
>> > > >
>> > > > [ ] -1 Do not release this package because …
>> > > >
>> > > > 38 tickets were resolved and release report is available here :
>> > > >
>> > > > https://s.apache.org/0.9GoraReleaseNotes
>> > > >
>> > > > Source release artifacts are available here :
>> > > >
>> > > > https://dist.apache.org/repos/dist/dev/gora/apache-gora-0.9-RC01/
>> > > >
>> > > > Staging repository is available here :
>> > > >
>> > > >
>> https://repository.apache.org/content/repositories/orgapachegora-1010
>> > > >
>> > > > Release candidate is signed through the key A3E66AC7 which is
>> available
>> > > > here :
>> > > >
>> > > > https://dist.apache.org/repos/dist/dev/gora/KEYS
>> > > >
>> > > > The release candidate is based on the sources tagged with
>> > > apache-gora-0.9:
>> > > >
>> > > >
>> > > >
>> > >
>> >
>> https://gitbox.apache.org/repos/asf?p=gora.git;a=tag;h=61b9a928a076a52a39f1b0771798bbae4742fffc
>> > > >
>> > > > and is based on the following commit id:
>> > > >
>> > > > 4b27f2bfebee1a77f9b957929c956ea1b509f9fb
>> > > >
>> > > > Thank you to everyone that contributed to Apache Gora 0.9 and who
>> are
>> > > able
>> > > > to vote on the release candidate.
>> > > >
>> > > > PS: My vote is `[x] +1 Release this package as Apache Gora 0.9`.
>> > > >
>> > > > Regards
>> > > >
>> > > > Kevin
>> > > >
>> > > >
>> > >
>> >
>>
>

Reply via email to