Paul, On Wed, Jul 27, 2016 at 10:00 AM, Paul Grosu <pgr...@gmail.com> wrote:
> > I understand the need, but rushing things with a complex programming > project such as this does not always translate into quality. With this > project I would prefer Google to take their time to do it right. The gRPC > team are doing fantastic service, but already they feel way too stretched > out in terms of resources, and that can be clearly seen from some of the > reverted pull requests > > Lately PRs have been flying off the shelf more frequently than usual - > assuming in preparation for the GA release, which is listed as 2 months > behind schedule - and there are still 111 PRs with 554 open issues in the > queue on Github. Once things stabilize, then maybe we can revisit > something that would be testable as a release candidate. We don't even > have the step-wise design specifications for the project - including target > features for release - and the project's guide for the team seems to be > just a spreadsheet. > In the interests of efficiency we have tried to use GitHub milestones to communicate what would be in a specific release. Take a look at some of the 1.1 milestones for features that have been pushed to 'next' Going forward we'll probably assess whether the use of milestones was an effective form of communication, it's certainly been a challenge to lean on GitHub while communicating progress on features that span several projects. This is definitely an area we'll try to do better on going forward > This approach has always proven true in all the places that I worked. > > Paul > > On Wednesday, July 27, 2016 at 10:11:41 AM UTC-4, jdov...@gmail.com wrote: >> >> Thanks for the replies. >> >> Initially my main uses will be in Java, Node, and C#. >> >> >> >> On Tuesday, July 26, 2016 at 8:32:35 PM UTC-7, Nathaniel Manista wrote: >>> >>> On Tue, Jul 26, 2016 at 8:56 AM, <jdov...@gmail.com> wrote: >>> >>>> I know that different parts of gRPC are more mature than others but in >>>> general how far are we from a formal release candidate? >>>> >>> >>> If you're working in Python, the current grpcio package is 1.0.0rc1 >>> <https://pypi.python.org/pypi/grpcio/1.0.0rc1> with the "rc" indicating >>> that it is a release candidate. >>> -Nathaniel >>> >> -- > You received this message because you are subscribed to the Google Groups " > grpc.io" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to grpc-io+unsubscr...@googlegroups.com. > To post to this group, send email to grpc-io@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/grpc-io/bee7c8d3-8718-46cb-9107-b8f5a67b6a23%40googlegroups.com > <https://groups.google.com/d/msgid/grpc-io/bee7c8d3-8718-46cb-9107-b8f5a67b6a23%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+unsubscr...@googlegroups.com. To post to this group, send email to grpc-io@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/CADQ0XY1SGxjDgwAyd9KmMMGLhjdGVLMo6CYHjG8owMSZLrJDuw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
