You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cassandra.apache.org by Mick Semb Wever <mc...@apache.org> on 2020/01/30 19:46:35 UTC
[VOTE] Release Apache Cassandra 4.0-alpha3
Proposing the test build of Cassandra 4.0-alpha3 for release.
sha1: 5f7c88601c65cdf14ee68387ed68203f2603fc29
Git: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-alpha3-tentative
Maven Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1189/org/apache/cassandra/apache-cassandra/4.0-alpha3/
The Source and Build Artifacts, and the Debian and RPM packages are available here: https://dist.apache.org/repos/dist/dev/cassandra/4.0-alpha3/
The vote will be open for 72 hours (longer if needed). Everyone who has tested the build is invited to vote. Votes by PMC members are considered binding. A vote passes if there are at least three binding +1s.
** Please note this is my first time as release manager, and the release process has been improved to deal with sha256|512 checksums as well as to use the ASF dev dist staging location. So please be extra critical. **
[1]: CHANGES.txt: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-alpha3-tentative
[2]: NEWS.txt: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0-alpha3-tentative
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org
Re: [VOTE] Release Apache Cassandra 4.0-alpha3
Posted by Michael Shuler <mi...@pbandjelly.org>.
On 2/4/20 3:59 PM, Mick Semb Wever wrote:
>
>> Proposing the test build of Cassandra 4.0-alpha3 for release.
>>
>> sha1: 5f7c88601c65cdf14ee68387ed68203f2603fc29
>> Git:
>> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-alpha3-tentative
>> Maven Artifacts:
>> https://repository.apache.org/content/repositories/orgapachecassandra-1189/org/apache/cassandra/apache-cassandra/4.0-alpha3/
>>
>> The Source and Build Artifacts, and the Debian and RPM packages are
>> available here:
>> https://dist.apache.org/repos/dist/dev/cassandra/4.0-alpha3/
>>
>> The vote will be open for 72 hours (longer if needed). Everyone who has
>> tested the build is invited to vote. Votes by PMC members are
>> considered binding. A vote passes if there are at least three binding
>> +1s.
>
>
> This vote has passed after 5 days with 4 binding votes and 3 non-binding votes.
>
> The publishing of the release needs to be handed over to a PMC to do, but in coordination with the improvements to the release process being done in CASSANDRA-14970, so a little patience please. Once this is done I will address CASSANDRA-15541 and then am hoping to cut and raise the votes for the releases for 2.2.16, 3.0.20, 3.11.6. If no one objects.
Mick pinged me on slack, so fyi here, too - I'll work on this in the
morning if I can't get it in tonight.
--
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org
Re: [VOTE] Release Apache Cassandra 4.0-alpha3
Posted by Mick Semb Wever <mc...@apache.org>.
> Proposing the test build of Cassandra 4.0-alpha3 for release.
>
> sha1: 5f7c88601c65cdf14ee68387ed68203f2603fc29
> Git:
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-alpha3-tentative
> Maven Artifacts:
> https://repository.apache.org/content/repositories/orgapachecassandra-1189/org/apache/cassandra/apache-cassandra/4.0-alpha3/
>
> The Source and Build Artifacts, and the Debian and RPM packages are
> available here:
> https://dist.apache.org/repos/dist/dev/cassandra/4.0-alpha3/
>
> The vote will be open for 72 hours (longer if needed). Everyone who has
> tested the build is invited to vote. Votes by PMC members are
> considered binding. A vote passes if there are at least three binding
> +1s.
This vote has passed after 5 days with 4 binding votes and 3 non-binding votes.
The publishing of the release needs to be handed over to a PMC to do, but in coordination with the improvements to the release process being done in CASSANDRA-14970, so a little patience please. Once this is done I will address CASSANDRA-15541 and then am hoping to cut and raise the votes for the releases for 2.2.16, 3.0.20, 3.11.6. If no one objects.
regards,
Mick
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org
Re: [VOTE] Release Apache Cassandra 4.0-alpha3
Posted by Yuji Ito <yu...@phact-columba.com>.
+1 (non-binding)
I've briefly tested the build with Jepsen.
https://github.com/scalar-labs/scalar-jepsen
2020年1月31日(金) 13:37 Anthony Grasso <an...@gmail.com>:
> +1 (non-binding)
>
> On Fri, 31 Jan 2020 at 08:48, Joshua McKenzie <jm...@apache.org>
> wrote:
>
> > +1
> >
> > On Thu, Jan 30, 2020 at 4:31 PM Brandon Williams <dr...@gmail.com>
> wrote:
> >
> > > +1
> > >
> > > On Thu, Jan 30, 2020 at 1:47 PM Mick Semb Wever <mc...@apache.org>
> wrote:
> > > >
> > > > Proposing the test build of Cassandra 4.0-alpha3 for release.
> > > >
> > > > sha1: 5f7c88601c65cdf14ee68387ed68203f2603fc29
> > > > Git:
> > >
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-alpha3-tentative
> > > > Maven Artifacts:
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-1189/org/apache/cassandra/apache-cassandra/4.0-alpha3/
> > > >
> > > > The Source and Build Artifacts, and the Debian and RPM packages are
> > > available here:
> > > https://dist.apache.org/repos/dist/dev/cassandra/4.0-alpha3/
> > > >
> > > > The vote will be open for 72 hours (longer if needed). Everyone who
> has
> > > tested the build is invited to vote. Votes by PMC members are
> considered
> > > binding. A vote passes if there are at least three binding +1s.
> > > >
> > > > ** Please note this is my first time as release manager, and the
> > release
> > > process has been improved to deal with sha256|512 checksums as well as
> to
> > > use the ASF dev dist staging location. So please be extra critical. **
> > > >
> > > >
> > > > [1]: CHANGES.txt:
> > >
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-alpha3-tentative
> > > > [2]: NEWS.txt:
> > >
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0-alpha3-tentative
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> > > > For additional commands, e-mail: dev-help@cassandra.apache.org
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> > > For additional commands, e-mail: dev-help@cassandra.apache.org
> > >
> > >
> >
>
Re: [VOTE] Release Apache Cassandra 4.0-alpha3
Posted by Anthony Grasso <an...@gmail.com>.
+1 (non-binding)
On Fri, 31 Jan 2020 at 08:48, Joshua McKenzie <jm...@apache.org> wrote:
> +1
>
> On Thu, Jan 30, 2020 at 4:31 PM Brandon Williams <dr...@gmail.com> wrote:
>
> > +1
> >
> > On Thu, Jan 30, 2020 at 1:47 PM Mick Semb Wever <mc...@apache.org> wrote:
> > >
> > > Proposing the test build of Cassandra 4.0-alpha3 for release.
> > >
> > > sha1: 5f7c88601c65cdf14ee68387ed68203f2603fc29
> > > Git:
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-alpha3-tentative
> > > Maven Artifacts:
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-1189/org/apache/cassandra/apache-cassandra/4.0-alpha3/
> > >
> > > The Source and Build Artifacts, and the Debian and RPM packages are
> > available here:
> > https://dist.apache.org/repos/dist/dev/cassandra/4.0-alpha3/
> > >
> > > The vote will be open for 72 hours (longer if needed). Everyone who has
> > tested the build is invited to vote. Votes by PMC members are considered
> > binding. A vote passes if there are at least three binding +1s.
> > >
> > > ** Please note this is my first time as release manager, and the
> release
> > process has been improved to deal with sha256|512 checksums as well as to
> > use the ASF dev dist staging location. So please be extra critical. **
> > >
> > >
> > > [1]: CHANGES.txt:
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-alpha3-tentative
> > > [2]: NEWS.txt:
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0-alpha3-tentative
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> > > For additional commands, e-mail: dev-help@cassandra.apache.org
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> > For additional commands, e-mail: dev-help@cassandra.apache.org
> >
> >
>
Re: [VOTE] Release Apache Cassandra 4.0-alpha3
Posted by Joshua McKenzie <jm...@apache.org>.
+1
On Thu, Jan 30, 2020 at 4:31 PM Brandon Williams <dr...@gmail.com> wrote:
> +1
>
> On Thu, Jan 30, 2020 at 1:47 PM Mick Semb Wever <mc...@apache.org> wrote:
> >
> > Proposing the test build of Cassandra 4.0-alpha3 for release.
> >
> > sha1: 5f7c88601c65cdf14ee68387ed68203f2603fc29
> > Git:
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-alpha3-tentative
> > Maven Artifacts:
> https://repository.apache.org/content/repositories/orgapachecassandra-1189/org/apache/cassandra/apache-cassandra/4.0-alpha3/
> >
> > The Source and Build Artifacts, and the Debian and RPM packages are
> available here:
> https://dist.apache.org/repos/dist/dev/cassandra/4.0-alpha3/
> >
> > The vote will be open for 72 hours (longer if needed). Everyone who has
> tested the build is invited to vote. Votes by PMC members are considered
> binding. A vote passes if there are at least three binding +1s.
> >
> > ** Please note this is my first time as release manager, and the release
> process has been improved to deal with sha256|512 checksums as well as to
> use the ASF dev dist staging location. So please be extra critical. **
> >
> >
> > [1]: CHANGES.txt:
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-alpha3-tentative
> > [2]: NEWS.txt:
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0-alpha3-tentative
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> > For additional commands, e-mail: dev-help@cassandra.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> For additional commands, e-mail: dev-help@cassandra.apache.org
>
>
Re: [VOTE] Release Apache Cassandra 4.0-alpha3
Posted by Brandon Williams <dr...@gmail.com>.
+1
On Thu, Jan 30, 2020 at 1:47 PM Mick Semb Wever <mc...@apache.org> wrote:
>
> Proposing the test build of Cassandra 4.0-alpha3 for release.
>
> sha1: 5f7c88601c65cdf14ee68387ed68203f2603fc29
> Git: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-alpha3-tentative
> Maven Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1189/org/apache/cassandra/apache-cassandra/4.0-alpha3/
>
> The Source and Build Artifacts, and the Debian and RPM packages are available here: https://dist.apache.org/repos/dist/dev/cassandra/4.0-alpha3/
>
> The vote will be open for 72 hours (longer if needed). Everyone who has tested the build is invited to vote. Votes by PMC members are considered binding. A vote passes if there are at least three binding +1s.
>
> ** Please note this is my first time as release manager, and the release process has been improved to deal with sha256|512 checksums as well as to use the ASF dev dist staging location. So please be extra critical. **
>
>
> [1]: CHANGES.txt: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-alpha3-tentative
> [2]: NEWS.txt: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0-alpha3-tentative
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> For additional commands, e-mail: dev-help@cassandra.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org
Re: [VOTE] Release Apache Cassandra 4.0-alpha3
Posted by Dinesh Joshi <dj...@apache.org>.
I’ve fixed the failing timestamps related cqlsh dtests in my 10190 branch which hasn’t yet been merged. It’s a known issue related to 15257 (more context in there). The test needs to be adjusted for new time stamp formats.
Dinesh
> On Feb 4, 2020, at 10:19 AM, Sumanth Pasupuleti <su...@gmail.com> wrote:
>
> Java8 Test run summary for 4.0-alpha3-tentative
> Passing UTs: https://circleci.com/gh/sumanth-pasupuleti/cassandra/852
> Passing jvm_dtests: https://circleci.com/gh/sumanth-pasupuleti/cassandra/853
> 1 failing dtest (
> https://circleci.com/gh/sumanth-pasupuleti/cassandra/855#tests/containers/92
> ,
> https://circleci.com/gh/sumanth-pasupuleti/cassandra/854#tests/containers/96
> )
> test_datetime_values - cqlsh_tests.test_cqlsh.TestCqlsh
> cqlsh_tests/test_cqlsh.py
>
> more
> AssertionError: Failed to execute cqlsh: <stdin>:13:InvalidRequest:
> Error from server: code=2200 [Invalid query] message="Unable to coerce
> '1582-1-1' to a formatted date (long)" <stdin>:15:InvalidRequest:
> Error from server: code=2200 [Invalid query] message="Unable to coerce
> '0-1-1' to a formatted date (long)" <stdin>:17:InvalidRequest: Error
> from server: code=2200 [Invalid query] message="Unable to coerce
> '1-1-1' to a formatted date (long)" <stdin>:19:InvalidRequest: Error
> from server: code=2200 [Invalid query] message="Unable to coerce
> '9999-1-1' to a formatted date (long)" <stdin>:21:InvalidRequest:
> Error from server: code=2200 [Invalid query] message="Unable to coerce
> '10000-1-1' to a formatted date (long)" assert 0 == 680 + where
> 680 = len('<stdin>:13:InvalidRequest: Error from server: code=2200
> [Invalid query] message="Unable to coerce \'1582-1-1\' to a f...st:
> Error from server: code=2200 [Invalid query] message="Unable to coerce
> \'10000-1-1\' to a formatted date (long)"\n')
>
>
> Thanks,
> Sumanth
>
>> On Mon, Feb 3, 2020 at 7:09 PM Michael Shuler <mi...@pbandjelly.org>
>> wrote:
>>
>>> On 2/3/20 5:21 PM, Mick Semb Wever wrote:
>>>
>>>> Summary of notes:
>>>> - Artifact set checks out OK with regards to key sigs and checksums.
>>>> - CASSANDRA-14962 is an issue when not using the current deb build
>>>> method (using new docker method results in different source artifact
>>>> creation & use). The docker rpm build suffers the same source problem
>>>> and the src.rpm is significantly larger, since I think it copies all the
>>>> downloaded maven artifacts in. It's fine for now, though :)
>>>> - UNRELEASED deb build
>>>
>>>
>>> Thanks for the thorough review Michael.
>>>
>>> I did not know about CASSANDRA-14962, but it should be easy to fix now
>> that the -src.tar.gz is in the dev dist location and easy to re-use. I'll
>> see if I can create a patch for that (aiming to use it on alpha4).
>>
>> Yep! Similarly, the rpm build has been wrong all along, but it's what we
>> have. The -src.tar.gz should get copied to /$build/$path/SOURCE dir, I
>> think it is(?). I think that might cure the larger .src.rpm.
>>
>>> And I was unaware of the UNRELEASED version issue. I can put a patch in
>> for that too, going into the prepare_release.sh script.
>>
>> `dch -r` is usually a step I do before building, also checking NEWS and
>> CHANGES and build.xml versions all align. Then the correct commit gets
>> -tentative tagged. Building `dch -r` in would be OK, if all the other
>> ducks are in a row.
>>
>>>> Next step
>>>> would be to do each package-type install and startup functional testing,
>>>> but I don't have that time right now :)
>>>
>>>
>>> I'm going to presume others that have voted have done package-type
>> installs and the basic testing, and move ahead. If I close the vote, I will
>> need your help Michael with the final steps running the patched
>> finish_release.sh from the `mck/14970_sha512-checksums` branch, found in
>> https://github.com/thelastpickle/cassandra-builds/blob/mck/14970_sha512-checksums/
>>> Because only PMC can `svn move` the files into
>> dist.apache.org/repos/dist/release/
>>
>> I usually do this before vote. I don't know how many other people, if
>> any, test that all the packages can install and start.
>>
>>> And for the upload_bintray.sh script, how do I get credentials, an infra
>> ticket i presume? (ie to https://bintray.com/apache )
>>
>> If I recall, I did an infra ticket with my github user id - this is how
>> I log in. Once logged into bintray, you can find a token down in the
>> user profile somewhere, which is used in the script.
>>
>> Thanks again for walking through these steps.
>>
>> Michael
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
>> For additional commands, e-mail: dev-help@cassandra.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org
Re: [VOTE] Release Apache Cassandra 4.0-alpha3
Posted by Sumanth Pasupuleti <su...@gmail.com>.
Java8 Test run summary for 4.0-alpha3-tentative
Passing UTs: https://circleci.com/gh/sumanth-pasupuleti/cassandra/852
Passing jvm_dtests: https://circleci.com/gh/sumanth-pasupuleti/cassandra/853
1 failing dtest (
https://circleci.com/gh/sumanth-pasupuleti/cassandra/855#tests/containers/92
,
https://circleci.com/gh/sumanth-pasupuleti/cassandra/854#tests/containers/96
)
test_datetime_values - cqlsh_tests.test_cqlsh.TestCqlsh
cqlsh_tests/test_cqlsh.py
more
AssertionError: Failed to execute cqlsh: <stdin>:13:InvalidRequest:
Error from server: code=2200 [Invalid query] message="Unable to coerce
'1582-1-1' to a formatted date (long)" <stdin>:15:InvalidRequest:
Error from server: code=2200 [Invalid query] message="Unable to coerce
'0-1-1' to a formatted date (long)" <stdin>:17:InvalidRequest: Error
from server: code=2200 [Invalid query] message="Unable to coerce
'1-1-1' to a formatted date (long)" <stdin>:19:InvalidRequest: Error
from server: code=2200 [Invalid query] message="Unable to coerce
'9999-1-1' to a formatted date (long)" <stdin>:21:InvalidRequest:
Error from server: code=2200 [Invalid query] message="Unable to coerce
'10000-1-1' to a formatted date (long)" assert 0 == 680 + where
680 = len('<stdin>:13:InvalidRequest: Error from server: code=2200
[Invalid query] message="Unable to coerce \'1582-1-1\' to a f...st:
Error from server: code=2200 [Invalid query] message="Unable to coerce
\'10000-1-1\' to a formatted date (long)"\n')
Thanks,
Sumanth
On Mon, Feb 3, 2020 at 7:09 PM Michael Shuler <mi...@pbandjelly.org>
wrote:
> On 2/3/20 5:21 PM, Mick Semb Wever wrote:
> >
> >> Summary of notes:
> >> - Artifact set checks out OK with regards to key sigs and checksums.
> >> - CASSANDRA-14962 is an issue when not using the current deb build
> >> method (using new docker method results in different source artifact
> >> creation & use). The docker rpm build suffers the same source problem
> >> and the src.rpm is significantly larger, since I think it copies all the
> >> downloaded maven artifacts in. It's fine for now, though :)
> >> - UNRELEASED deb build
> >
> >
> > Thanks for the thorough review Michael.
> >
> > I did not know about CASSANDRA-14962, but it should be easy to fix now
> that the -src.tar.gz is in the dev dist location and easy to re-use. I'll
> see if I can create a patch for that (aiming to use it on alpha4).
>
> Yep! Similarly, the rpm build has been wrong all along, but it's what we
> have. The -src.tar.gz should get copied to /$build/$path/SOURCE dir, I
> think it is(?). I think that might cure the larger .src.rpm.
>
> > And I was unaware of the UNRELEASED version issue. I can put a patch in
> for that too, going into the prepare_release.sh script.
>
> `dch -r` is usually a step I do before building, also checking NEWS and
> CHANGES and build.xml versions all align. Then the correct commit gets
> -tentative tagged. Building `dch -r` in would be OK, if all the other
> ducks are in a row.
>
> >> Next step
> >> would be to do each package-type install and startup functional testing,
> >> but I don't have that time right now :)
> >
> >
> > I'm going to presume others that have voted have done package-type
> installs and the basic testing, and move ahead. If I close the vote, I will
> need your help Michael with the final steps running the patched
> finish_release.sh from the `mck/14970_sha512-checksums` branch, found in
> https://github.com/thelastpickle/cassandra-builds/blob/mck/14970_sha512-checksums/
> > Because only PMC can `svn move` the files into
> dist.apache.org/repos/dist/release/
>
> I usually do this before vote. I don't know how many other people, if
> any, test that all the packages can install and start.
>
> > And for the upload_bintray.sh script, how do I get credentials, an infra
> ticket i presume? (ie to https://bintray.com/apache )
>
> If I recall, I did an infra ticket with my github user id - this is how
> I log in. Once logged into bintray, you can find a token down in the
> user profile somewhere, which is used in the script.
>
> Thanks again for walking through these steps.
>
> Michael
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> For additional commands, e-mail: dev-help@cassandra.apache.org
>
>
Re: [VOTE] Release Apache Cassandra 4.0-alpha3
Posted by Mick Semb Wever <mc...@apache.org>.
> >> Next step would be to do each package-type install and startup functional testing,
> >> but I don't have that time right now :)
> >
> >
> > I'm going to presume others that have voted have done package-type installs and the basic testing, and move ahead. [snip]
>
> I usually do this before vote. I don't know how many other people, if
> any, test that all the packages can install and start.
done.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org
Re: [VOTE] Release Apache Cassandra 4.0-alpha3
Posted by Michael Shuler <mi...@pbandjelly.org>.
On 2/3/20 5:21 PM, Mick Semb Wever wrote:
>
>> Summary of notes:
>> - Artifact set checks out OK with regards to key sigs and checksums.
>> - CASSANDRA-14962 is an issue when not using the current deb build
>> method (using new docker method results in different source artifact
>> creation & use). The docker rpm build suffers the same source problem
>> and the src.rpm is significantly larger, since I think it copies all the
>> downloaded maven artifacts in. It's fine for now, though :)
>> - UNRELEASED deb build
>
>
> Thanks for the thorough review Michael.
>
> I did not know about CASSANDRA-14962, but it should be easy to fix now that the -src.tar.gz is in the dev dist location and easy to re-use. I'll see if I can create a patch for that (aiming to use it on alpha4).
Yep! Similarly, the rpm build has been wrong all along, but it's what we
have. The -src.tar.gz should get copied to /$build/$path/SOURCE dir, I
think it is(?). I think that might cure the larger .src.rpm.
> And I was unaware of the UNRELEASED version issue. I can put a patch in for that too, going into the prepare_release.sh script.
`dch -r` is usually a step I do before building, also checking NEWS and
CHANGES and build.xml versions all align. Then the correct commit gets
-tentative tagged. Building `dch -r` in would be OK, if all the other
ducks are in a row.
>> Next step
>> would be to do each package-type install and startup functional testing,
>> but I don't have that time right now :)
>
>
> I'm going to presume others that have voted have done package-type installs and the basic testing, and move ahead. If I close the vote, I will need your help Michael with the final steps running the patched finish_release.sh from the `mck/14970_sha512-checksums` branch, found in https://github.com/thelastpickle/cassandra-builds/blob/mck/14970_sha512-checksums/
> Because only PMC can `svn move` the files into dist.apache.org/repos/dist/release/
I usually do this before vote. I don't know how many other people, if
any, test that all the packages can install and start.
> And for the upload_bintray.sh script, how do I get credentials, an infra ticket i presume? (ie to https://bintray.com/apache )
If I recall, I did an infra ticket with my github user id - this is how
I log in. Once logged into bintray, you can find a token down in the
user profile somewhere, which is used in the script.
Thanks again for walking through these steps.
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org
Re: [VOTE] Release Apache Cassandra 4.0-alpha3
Posted by Dinesh Joshi <dj...@apache.org>.
+1, this at least starts up on Windows ;)
Dinesh
> On Feb 3, 2020, at 3:21 PM, Mick Semb Wever <mc...@apache.org> wrote:
>
>
>> Summary of notes:
>> - Artifact set checks out OK with regards to key sigs and checksums.
>> - CASSANDRA-14962 is an issue when not using the current deb build
>> method (using new docker method results in different source artifact
>> creation & use). The docker rpm build suffers the same source problem
>> and the src.rpm is significantly larger, since I think it copies all the
>> downloaded maven artifacts in. It's fine for now, though :)
>> - UNRELEASED deb build
>
>
> Thanks for the thorough review Michael.
>
> I did not know about CASSANDRA-14962, but it should be easy to fix now that the -src.tar.gz is in the dev dist location and easy to re-use. I'll see if I can create a patch for that (aiming to use it on alpha4).
>
> And I was unaware of the UNRELEASED version issue. I can put a patch in for that too, going into the prepare_release.sh script.
>
>
>> Next step
>> would be to do each package-type install and startup functional testing,
>> but I don't have that time right now :)
>
>
> I'm going to presume others that have voted have done package-type installs and the basic testing, and move ahead. If I close the vote, I will need your help Michael with the final steps running the patched finish_release.sh from the `mck/14970_sha512-checksums` branch, found in https://github.com/thelastpickle/cassandra-builds/blob/mck/14970_sha512-checksums/
> Because only PMC can `svn move` the files into dist.apache.org/repos/dist/release/
>
> And for the upload_bintray.sh script, how do I get credentials, an infra ticket i presume? (ie to https://bintray.com/apache )
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> For additional commands, e-mail: dev-help@cassandra.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org
Re: [VOTE] Release Apache Cassandra 4.0-alpha3
Posted by Mick Semb Wever <mc...@apache.org>.
> Summary of notes:
> - Artifact set checks out OK with regards to key sigs and checksums.
> - CASSANDRA-14962 is an issue when not using the current deb build
> method (using new docker method results in different source artifact
> creation & use). The docker rpm build suffers the same source problem
> and the src.rpm is significantly larger, since I think it copies all the
> downloaded maven artifacts in. It's fine for now, though :)
> - UNRELEASED deb build
Thanks for the thorough review Michael.
I did not know about CASSANDRA-14962, but it should be easy to fix now that the -src.tar.gz is in the dev dist location and easy to re-use. I'll see if I can create a patch for that (aiming to use it on alpha4).
And I was unaware of the UNRELEASED version issue. I can put a patch in for that too, going into the prepare_release.sh script.
> Next step
> would be to do each package-type install and startup functional testing,
> but I don't have that time right now :)
I'm going to presume others that have voted have done package-type installs and the basic testing, and move ahead. If I close the vote, I will need your help Michael with the final steps running the patched finish_release.sh from the `mck/14970_sha512-checksums` branch, found in https://github.com/thelastpickle/cassandra-builds/blob/mck/14970_sha512-checksums/
Because only PMC can `svn move` the files into dist.apache.org/repos/dist/release/
And for the upload_bintray.sh script, how do I get credentials, an infra ticket i presume? (ie to https://bintray.com/apache )
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org
Re: [VOTE] Release Apache Cassandra 4.0-alpha3
Posted by Michael Shuler <mi...@pbandjelly.org>.
+1, with notes attached.
Thanks for this release build, Mick - good work.
Summary of notes:
- Artifact set checks out OK with regards to key sigs and checksums.
- CASSANDRA-14962 is an issue when not using the current deb build
method (using new docker method results in different source artifact
creation & use). The docker rpm build suffers the same source problem
and the src.rpm is significantly larger, since I think it copies all the
downloaded maven artifacts in. It's fine for now, though :)
- UNRELEASED deb build
If anyone is interested in some basic quick download allthethings and
check 'em, commands and console txt might be interesting. Next step
would be to do each package-type install and startup functional testing,
but I don't have that time right now :)
Warm regards,
Michael
On 1/30/20 1:46 PM, Mick Semb Wever wrote:
> Proposing the test build of Cassandra 4.0-alpha3 for release.
>
> sha1: 5f7c88601c65cdf14ee68387ed68203f2603fc29
> Git: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-alpha3-tentative
> Maven Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1189/org/apache/cassandra/apache-cassandra/4.0-alpha3/
>
> The Source and Build Artifacts, and the Debian and RPM packages are available here: https://dist.apache.org/repos/dist/dev/cassandra/4.0-alpha3/
>
> The vote will be open for 72 hours (longer if needed). Everyone who has tested the build is invited to vote. Votes by PMC members are considered binding. A vote passes if there are at least three binding +1s.
>
> ** Please note this is my first time as release manager, and the release process has been improved to deal with sha256|512 checksums as well as to use the ASF dev dist staging location. So please be extra critical. **
>
>
> [1]: CHANGES.txt: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-alpha3-tentative
> [2]: NEWS.txt: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0-alpha3-tentative
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> For additional commands, e-mail: dev-help@cassandra.apache.org
>
Re: [VOTE] Release Apache Cassandra 4.0-alpha3
Posted by Nate McCall <zz...@gmail.com>.
+1
Thanks for getting this started, Mick!
On Fri, Jan 31, 2020 at 8:47 AM Mick Semb Wever <mc...@apache.org> wrote:
> Proposing the test build of Cassandra 4.0-alpha3 for release.
>
> sha1: 5f7c88601c65cdf14ee68387ed68203f2603fc29
> Git:
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-alpha3-tentative
> Maven Artifacts:
> https://repository.apache.org/content/repositories/orgapachecassandra-1189/org/apache/cassandra/apache-cassandra/4.0-alpha3/
>
> The Source and Build Artifacts, and the Debian and RPM packages are
> available here:
> https://dist.apache.org/repos/dist/dev/cassandra/4.0-alpha3/
>
> The vote will be open for 72 hours (longer if needed). Everyone who has
> tested the build is invited to vote. Votes by PMC members are considered
> binding. A vote passes if there are at least three binding +1s.
>
> ** Please note this is my first time as release manager, and the release
> process has been improved to deal with sha256|512 checksums as well as to
> use the ASF dev dist staging location. So please be extra critical. **
>
>
> [1]: CHANGES.txt:
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-alpha3-tentative
> [2]: NEWS.txt:
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0-alpha3-tentative
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> For additional commands, e-mail: dev-help@cassandra.apache.org
>
>