You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by Stig Rohde Døssing <st...@gmail.com> on 2019/08/01 09:25:40 UTC
Re: [DISCUSS] Create a checklist for testing new Storm release
The list looks good. I think we should drop the .md5 files, the ASF have
been telling people not to use them for a while.
I don't know that everyone needs to do it, but someone should check that
the license files are up to date, and that we're not including any
dependencies with incompatible licenses (
https://apache.org/legal/resolved.html). Ideally we can automate most of
the work.
Den man. 29. jul. 2019 kl. 23.56 skrev Ethan Li <et...@gmail.com>:
>
> Per Hugo’s suggestion, we should probably document the testings that every
> contributors/committers should do to guarantee a stable release. It also
> helps creating a check form or email template.
>
>
> The testings I did for 2.0.0 release are
>
> 1. Verify files such as *.asc, *.md5, *.sha512
> 2. Build Storm source code and run unit tests; create a Storm distribution.
> 3. Set up a standalone cluster using apache-storm-xxx.zip,
> apache-storm-xxx.tar.gz, the Storm distribution created from step 2,
> separately
> 4. Launch WordCountTopology and ThroughputVsLatency topology and check
> logs, UI metrics
> 5. Test basic UI functionalities such as jstack, heap dump, deactivate,
> activate, rebalance, change log level, kill topology
>
>
> Please suggest anything that should be added so that we can document a
> base checklist that everyone can follow to test a new Storm release.
>
>
> Thanks,
> Ethan
Re: [DISCUSS] Create a checklist for testing new Storm release
Posted by Ethan Li <et...@gmail.com>.
Sorry for dragging on too long. I filed a PR
https://github.com/apache/storm/pull/3161.
On Sat, Aug 10, 2019 at 12:32 AM Roshan Naik <ro...@yahoo.com.invalid>
wrote:
> +1 that does look like a nice list.
> On Thursday, August 1, 2019, 09:30:24 AM PDT, Ethan Li <
> ethanopensource@gmail.com> wrote:
>
> Right. I found this
> http://www.apache.org/dev/release-distribution.html#sigs-and-sums <
> http://www.apache.org/dev/release-distribution.html#sigs-and-sums>
>
> In the new release, we should drop md5 checksum file.
>
>
> > On Aug 1, 2019, at 4:25 AM, Stig Rohde Døssing <st...@gmail.com>
> wrote:
> >
> > The list looks good. I think we should drop the .md5 files, the ASF have
> > been telling people not to use them for a while.
> >
> > I don't know that everyone needs to do it, but someone should check that
> > the license files are up to date, and that we're not including any
> > dependencies with incompatible licenses (
> > https://apache.org/legal/resolved.html). Ideally we can automate most of
> > the work.
> >
> > Den man. 29. jul. 2019 kl. 23.56 skrev Ethan Li <
> ethanopensource@gmail.com>:
> >
> >>
> >> Per Hugo’s suggestion, we should probably document the testings that
> every
> >> contributors/committers should do to guarantee a stable release. It also
> >> helps creating a check form or email template.
> >>
> >>
> >> The testings I did for 2.0.0 release are
> >>
> >> 1. Verify files such as *.asc, *.md5, *.sha512
> >> 2. Build Storm source code and run unit tests; create a Storm
> distribution.
> >> 3. Set up a standalone cluster using apache-storm-xxx.zip,
> >> apache-storm-xxx.tar.gz, the Storm distribution created from step 2,
> >> separately
> >> 4. Launch WordCountTopology and ThroughputVsLatency topology and check
> >> logs, UI metrics
> >> 5. Test basic UI functionalities such as jstack, heap dump, deactivate,
> >> activate, rebalance, change log level, kill topology
> >>
> >>
> >> Please suggest anything that should be added so that we can document a
> >> base checklist that everyone can follow to test a new Storm release.
> >>
> >>
> >> Thanks,
> >> Ethan
>
Re: [DISCUSS] Create a checklist for testing new Storm release
Posted by Roshan Naik <ro...@yahoo.com.INVALID>.
+1 that does look like a nice list.
On Thursday, August 1, 2019, 09:30:24 AM PDT, Ethan Li <et...@gmail.com> wrote:
Right. I found this http://www.apache.org/dev/release-distribution.html#sigs-and-sums <http://www.apache.org/dev/release-distribution.html#sigs-and-sums>
In the new release, we should drop md5 checksum file.
> On Aug 1, 2019, at 4:25 AM, Stig Rohde Døssing <st...@gmail.com> wrote:
>
> The list looks good. I think we should drop the .md5 files, the ASF have
> been telling people not to use them for a while.
>
> I don't know that everyone needs to do it, but someone should check that
> the license files are up to date, and that we're not including any
> dependencies with incompatible licenses (
> https://apache.org/legal/resolved.html). Ideally we can automate most of
> the work.
>
> Den man. 29. jul. 2019 kl. 23.56 skrev Ethan Li <et...@gmail.com>:
>
>>
>> Per Hugo’s suggestion, we should probably document the testings that every
>> contributors/committers should do to guarantee a stable release. It also
>> helps creating a check form or email template.
>>
>>
>> The testings I did for 2.0.0 release are
>>
>> 1. Verify files such as *.asc, *.md5, *.sha512
>> 2. Build Storm source code and run unit tests; create a Storm distribution.
>> 3. Set up a standalone cluster using apache-storm-xxx.zip,
>> apache-storm-xxx.tar.gz, the Storm distribution created from step 2,
>> separately
>> 4. Launch WordCountTopology and ThroughputVsLatency topology and check
>> logs, UI metrics
>> 5. Test basic UI functionalities such as jstack, heap dump, deactivate,
>> activate, rebalance, change log level, kill topology
>>
>>
>> Please suggest anything that should be added so that we can document a
>> base checklist that everyone can follow to test a new Storm release.
>>
>>
>> Thanks,
>> Ethan
Re: [DISCUSS] Create a checklist for testing new Storm release
Posted by Ethan Li <et...@gmail.com>.
Right. I found this http://www.apache.org/dev/release-distribution.html#sigs-and-sums <http://www.apache.org/dev/release-distribution.html#sigs-and-sums>
In the new release, we should drop md5 checksum file.
> On Aug 1, 2019, at 4:25 AM, Stig Rohde Døssing <st...@gmail.com> wrote:
>
> The list looks good. I think we should drop the .md5 files, the ASF have
> been telling people not to use them for a while.
>
> I don't know that everyone needs to do it, but someone should check that
> the license files are up to date, and that we're not including any
> dependencies with incompatible licenses (
> https://apache.org/legal/resolved.html). Ideally we can automate most of
> the work.
>
> Den man. 29. jul. 2019 kl. 23.56 skrev Ethan Li <et...@gmail.com>:
>
>>
>> Per Hugo’s suggestion, we should probably document the testings that every
>> contributors/committers should do to guarantee a stable release. It also
>> helps creating a check form or email template.
>>
>>
>> The testings I did for 2.0.0 release are
>>
>> 1. Verify files such as *.asc, *.md5, *.sha512
>> 2. Build Storm source code and run unit tests; create a Storm distribution.
>> 3. Set up a standalone cluster using apache-storm-xxx.zip,
>> apache-storm-xxx.tar.gz, the Storm distribution created from step 2,
>> separately
>> 4. Launch WordCountTopology and ThroughputVsLatency topology and check
>> logs, UI metrics
>> 5. Test basic UI functionalities such as jstack, heap dump, deactivate,
>> activate, rebalance, change log level, kill topology
>>
>>
>> Please suggest anything that should be added so that we can document a
>> base checklist that everyone can follow to test a new Storm release.
>>
>>
>> Thanks,
>> Ethan