Re: [VOTE] Pulsar Release 2.0.1-incubating Candidate 2
+1 (binding)
I checked:
Signing key, and verify the check sum.
License files and Notice files are OK
I can built the binary kit from source.
Please let me know when you commit the fix of source code license and clean
up the netty version issue.
I will keep an eye on the 2.1 branch to make sure those issue are fixed.
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Fri, Jun 15, 2018 at 5:22 AM, Matteo Merli wrote:
> Hi WIllem,
>
> the 2.0.1 candidate was already being voted on the dev@pulsar list when
> the
> comments on 1.22.1 release were made here on incubator list, otherwise we
> would have included the changes.
>
> 2.0.1 is a patch release in which we are trying to fix some issues reported
> by
> users in the 2.0.01-rc1 release from a couple of weeks back.
>
> Since at least a couple of issues were impacting users, we were trying to
> get
> a fix out ASAP. In particular we found packaging related issues that
> impacted:
> * Pulsar python client lib
> * Pulsar proxy startup
>
> Master branch is already set on 2.1 release and we just applied few commits
> to fix the non-functioning features.
>
> The idea was to fix netty packaging and protobuf license headers for 2.1,
> for
> which we plan to start the release process by next week.
>
> Matteo
>
> On Wed, Jun 13, 2018 at 6:24 PM Willem Jiang
> wrote:
>
> > Hi Matto,
> >
> > I just checked the source code, the License header issue is still there.
> > pulsar-common/src/main/java/org/apache/pulsar/common/util/
> > protobuf/ByteBufCoded{Input,Output}Stream.java
> >
> > There are still bunch different version of netty jars in the lib
> directory.
> >
> > My suggestion is we need fix these issues that we found in the last vote
> > before starting a new vote.
> >
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Tue, Jun 12, 2018 at 6:00 AM, Matteo Merli wrote:
> >
> > > This is the second release candidate for Apache Pulsar, version
> > > 2.0.1-incubating.
> > >
> > > Link to the vote on dev@pulsar list
> > > https://lists.apache.org/thread.html/620813d66d43a43680d3afd587e72f
> > > 0d6f9607f1566aa88ef73d359c@%3Cdev.pulsar.apache.org%3E
> > >
> > > Pulsar is a highly scalable, low latency messaging platform running on
> > > commodity hardware.
> > > It provides simple pub-sub semantics over topics, guaranteed
> > at-least-once
> > > delivery of
> > > messages, automatic cursor management for subscribers, and
> > geo-replication.
> > >
> > > This is a patch release that fixes few issues identified in previous
> > > release 2.0.0-rc1-incubating.
> > >
> > > It fixes the following issues:
> > > https://github.com/apache/incubator-pulsar/milestone/14?closed=1
> > >
> > > *** Please download, test and vote on this release. This vote will stay
> > > open
> > > for at least 72 hours ***
> > >
> > > Note that we are voting upon the source (tag), binaries are provided
> for
> > > convenience.
> > >
> > > Source and binary files:
> > > https://dist.apache.org/repos/dist/dev/incubator/pulsar/
> > > pulsar-2.0.1-incubating-candidate-2/
> > >
> > > SHA-1 checksums:
> > >
> > > 5acd63f8aa1fa75f386df7b9fd803a943978e609
> > > apache-pulsar-2.0.1-incubating-bin.tar.gz
> > > 312bc0f1ae170c1d2dc38b1e362fb50f82c00525
> > > apache-pulsar-2.0.1-incubating-src.tar.gz
> > >
> > > Maven staging repo:
> > > https://repository.apache.org/content/repositories/
> orgapachepulsar-1020
> > >
> > >
> > > The tag to be voted upon:
> > > v2.0.1-incubating-candidate-2 (fd47532380d770e4fd78cabe71dea2
> 93fc2f0e06)
> > > https://github.com/apache/incubator-pulsar/releases/tag/
> > > v2.0.1-incubating-candidate-2
> > > > > v2.0.1-incubating-candidate-1>
> > >
> > > Pulsar's KEYS file containing PGP keys we use to sign the release:
> > > https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS
> > >
> > > Please download the the source package, and follow the README to build
> > > and run the Pulsar standalone service.
> > > --
> > > Matteo Merli
> > >
> > >
> >
> --
> Matteo Merli
>
>
Re: [VOTE] Pulsar Release 2.0.1-incubating Candidate 2
Can anyone in IPMC help reviewing this? Since there are some user facing
issues reported at mailing lists and slack channel regarding 2.0.0 release,
we would like to get 2.0.1 release out as soon as this release passed
reviews.
Thank you,
Sijie
On Thu, Jun 14, 2018 at 2:22 PM Matteo Merli wrote:
> Hi WIllem,
>
> the 2.0.1 candidate was already being voted on the dev@pulsar list when
> the
> comments on 1.22.1 release were made here on incubator list, otherwise we
> would have included the changes.
>
> 2.0.1 is a patch release in which we are trying to fix some issues reported
> by
> users in the 2.0.01-rc1 release from a couple of weeks back.
>
> Since at least a couple of issues were impacting users, we were trying to
> get
> a fix out ASAP. In particular we found packaging related issues that
> impacted:
> * Pulsar python client lib
> * Pulsar proxy startup
>
> Master branch is already set on 2.1 release and we just applied few commits
> to fix the non-functioning features.
>
> The idea was to fix netty packaging and protobuf license headers for 2.1,
> for
> which we plan to start the release process by next week.
>
> Matteo
>
> On Wed, Jun 13, 2018 at 6:24 PM Willem Jiang
> wrote:
>
> > Hi Matto,
> >
> > I just checked the source code, the License header issue is still there.
> > pulsar-common/src/main/java/org/apache/pulsar/common/util/
> > protobuf/ByteBufCoded{Input,Output}Stream.java
> >
> > There are still bunch different version of netty jars in the lib
> directory.
> >
> > My suggestion is we need fix these issues that we found in the last vote
> > before starting a new vote.
> >
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Tue, Jun 12, 2018 at 6:00 AM, Matteo Merli wrote:
> >
> > > This is the second release candidate for Apache Pulsar, version
> > > 2.0.1-incubating.
> > >
> > > Link to the vote on dev@pulsar list
> > > https://lists.apache.org/thread.html/620813d66d43a43680d3afd587e72f
> > > 0d6f9607f1566aa88ef73d359c@%3Cdev.pulsar.apache.org%3E
> > >
> > > Pulsar is a highly scalable, low latency messaging platform running on
> > > commodity hardware.
> > > It provides simple pub-sub semantics over topics, guaranteed
> > at-least-once
> > > delivery of
> > > messages, automatic cursor management for subscribers, and
> > geo-replication.
> > >
> > > This is a patch release that fixes few issues identified in previous
> > > release 2.0.0-rc1-incubating.
> > >
> > > It fixes the following issues:
> > > https://github.com/apache/incubator-pulsar/milestone/14?closed=1
> > >
> > > *** Please download, test and vote on this release. This vote will stay
> > > open
> > > for at least 72 hours ***
> > >
> > > Note that we are voting upon the source (tag), binaries are provided
> for
> > > convenience.
> > >
> > > Source and binary files:
> > > https://dist.apache.org/repos/dist/dev/incubator/pulsar/
> > > pulsar-2.0.1-incubating-candidate-2/
> > >
> > > SHA-1 checksums:
> > >
> > > 5acd63f8aa1fa75f386df7b9fd803a943978e609
> > > apache-pulsar-2.0.1-incubating-bin.tar.gz
> > > 312bc0f1ae170c1d2dc38b1e362fb50f82c00525
> > > apache-pulsar-2.0.1-incubating-src.tar.gz
> > >
> > > Maven staging repo:
> > >
> https://repository.apache.org/content/repositories/orgapachepulsar-1020
> > >
> > >
> > > The tag to be voted upon:
> > > v2.0.1-incubating-candidate-2
> (fd47532380d770e4fd78cabe71dea293fc2f0e06)
> > > https://github.com/apache/incubator-pulsar/releases/tag/
> > > v2.0.1-incubating-candidate-2
> > > > > v2.0.1-incubating-candidate-1>
> > >
> > > Pulsar's KEYS file containing PGP keys we use to sign the release:
> > > https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS
> > >
> > > Please download the the source package, and follow the README to build
> > > and run the Pulsar standalone service.
> > > --
> > > Matteo Merli
> > >
> > >
> >
> --
> Matteo Merli
>
>
Re: Retiring legacy git repositories from podling?
+1 to a transfer rather than Attic. On Fri, Jun 15, 2018 at 2:05 AM, Stian Soiland-Reyes wrote: > Hi, > > The Taverna podling has its code in multiple git repositories > https://taverna.incubator.apache.org/code/ > Most of these were imported from the initial Software Grant > > > The Taverna PPMC has voted to retire two legacy git repositories that > will stay behind when/if we graduate. > > > https://github.com/apache/incubator-taverna-plugin-component > > https://github.com/apache/incubator-taverna-plugin-bioinformatics > > VOTE Result: > > https://lists.apache.org/thread.html/547b87fa93601d42ef77a778f80bf5 > 9fe9a300fffd7d3a6bcb7a7d81@%3Cdev.taverna.apache.org%3E > > > These code bases have NOT fully completed the IP clearance/license > checks (there would be a couple of files that have unknown authorship > or the odd GPL dependency), but have already got the Apache License > headers for the rest (majority) of the codebase, that was covered by > the Software Grant. Would we need to remove/change those headers? > > Do the IPMC need to vote on such 'retiring' of a code case? > > > Our plan is to do a GitHub owner transfer to our affiliated > https://github.com/taverna-extras/ -- but do let me know if you think > Apache Attic would be better (we could delete the files that miss the > headers). > > Do IPMC think that it's OK that we do such a GitHub transfer > (effectively giving a HTTP redirect) rather than just > forking+deleting? > > -- > Stian Soiland-Reyes > http://orcid.org/-0001-9842-9718 > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [ANNOUNCE] Apache SINGA (incubating) 1.2.0 released
Also you only need one KEYS link, and there should be a description of how to use KEYS + sig or hash to verify the downloads. On 15 June 2018 at 14:12, Craig Russell wrote: > Dear Singa project, > > Please update your download page to add links to the ASC signature files for > each of the artifacts. > > Regards, > > Craig > >> On Jun 14, 2018, at 6:51 PM, Moaz Reyad wrote: >> >> We are pleased to announce that SINGA (incubating) 1.2.0 is released. >> >> SINGA is a general distributed deep learning platform for training big deep >> learning models over large datasets. It is designed with an intuitive >> programming model based on the layer abstraction. SINGA supports a wide >> variety of popular deep learning models. >> >> The release is available at: >> http://singa.apache.org/en/downloads.html >> >> The main features of this release include: >> >> -Implement autograd (currently support MLP model) >> -Upgrade PySinga to support Python 3 >> -Improve the Tensor class with the stride field >> -Upgrade cuDNN from V5 to V7 >> -Add VGG, Inception V4, ResNet, and DenseNet for ImageNet classification >> -Create alias for conda packages >> -Complete documentation in Chinese >> -Add instructions for running SINGA on Windows >> -Update the compilation, CI >> >> We look forward to hearing your feedback, suggestions and contributions to >> the project. >> >> On behalf of the SINGA team, >> Moaz Reyad > > Craig L Russell > c...@apache.org > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [ANNOUNCE] Apache SINGA (incubating) 1.2.0 released
Dear Singa project, Please update your download page to add links to the ASC signature files for each of the artifacts. Regards, Craig > On Jun 14, 2018, at 6:51 PM, Moaz Reyad wrote: > > We are pleased to announce that SINGA (incubating) 1.2.0 is released. > > SINGA is a general distributed deep learning platform for training big deep > learning models over large datasets. It is designed with an intuitive > programming model based on the layer abstraction. SINGA supports a wide > variety of popular deep learning models. > > The release is available at: > http://singa.apache.org/en/downloads.html > > The main features of this release include: > > -Implement autograd (currently support MLP model) > -Upgrade PySinga to support Python 3 > -Improve the Tensor class with the stride field > -Upgrade cuDNN from V5 to V7 > -Add VGG, Inception V4, ResNet, and DenseNet for ImageNet classification > -Create alias for conda packages > -Complete documentation in Chinese > -Add instructions for running SINGA on Windows > -Update the compilation, CI > > We look forward to hearing your feedback, suggestions and contributions to > the project. > > On behalf of the SINGA team, > Moaz Reyad Craig L Russell c...@apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Retiring legacy git repositories from podling?
Hi, The Taverna podling has its code in multiple git repositories https://taverna.incubator.apache.org/code/ Most of these were imported from the initial Software Grant The Taverna PPMC has voted to retire two legacy git repositories that will stay behind when/if we graduate. > https://github.com/apache/incubator-taverna-plugin-component > https://github.com/apache/incubator-taverna-plugin-bioinformatics VOTE Result: https://lists.apache.org/thread.html/547b87fa93601d42ef77a778f80bf59fe9a300fffd7d3a6bcb7a7d81@%3Cdev.taverna.apache.org%3E These code bases have NOT fully completed the IP clearance/license checks (there would be a couple of files that have unknown authorship or the odd GPL dependency), but have already got the Apache License headers for the rest (majority) of the codebase, that was covered by the Software Grant. Would we need to remove/change those headers? Do the IPMC need to vote on such 'retiring' of a code case? Our plan is to do a GitHub owner transfer to our affiliated https://github.com/taverna-extras/ -- but do let me know if you think Apache Attic would be better (we could delete the files that miss the headers). Do IPMC think that it's OK that we do such a GitHub transfer (effectively giving a HTTP redirect) rather than just forking+deleting? -- Stian Soiland-Reyes http://orcid.org/-0001-9842-9718 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
