Remember there's no such thing as bad feedback. We want to know how it
works for you based on your typical usage case.

On Wed, Jul 27, 2016 at 5:49 PM, 'Kailash Sethuraman' via grpc.io <
[email protected]> wrote:

>
> At the moment, the website (grpc.io) documentation not fully reflect the
> pre-release. They reference the last full release, 0.15.
>
> I would recommend something in-between both the paths you mention. Try
> these packages in your test environments as you normally would, see if it
> works and report any unexpected behaviour.
>
> Branches for the code:
> https://github.com/grpc/grpc/tree/v1.0.x
> and
> https://github.com/grpc/grpc-java/tree/v1.0.x
>
> Hope that helps!
>
>
> On Wed, Jul 27, 2016 at 5:32 PM Paul Grosu <[email protected]> wrote:
>
>>
>> Hi Kailash,
>>
>> This is fantastic news!  Big Congratulations to the whole team!
>>
>> Just wondering how thoroughly should we test these releases?  Basically
>> should we put:
>>
>>    - A naive user hat (i.e. let me find the documentation and follow
>>    it), or
>>    - An expert user hat (i.e. let me tweak the Makefile and core code,
>>    and make it work for my instance)?
>>
>> Thanks,
>> Paul
>>
>>
>> On Wednesday, July 27, 2016 at 8:05:18 PM UTC-4, [email protected]
>> wrote:
>>>
>>> Hi Everyone,
>>>
>>>
>>> The gRPC team is pleased to announce that we have our first 1.0-pre
>>> packages ready for testing. Instructions and release notes below.
>>>
>>> Please give these a try and report any issues via our issue trackers on
>>> Github, it will help ensure that our 1.0 release is robust and works really
>>> well.
>>>
>>> Do note that this is a pre-release. We are currently working to update
>>> our documentation to reflect these changes and make any last minute changes
>>> before we release 1.0.
>>>
>>> Issue trackers:
>>>
>>> https://github.com/grpc/grpc/issues
>>>
>>> https://github.com/grpc/grpc-java/issues
>>>
>>> Notes on installation:
>>> Python:
>>>
>>> pip install --pre grpcio
>>>
>>> pip install --pre  grpcio-tools
>>> Ruby:
>>>
>>> gem install grpc --pre
>>>
>>> gem install grpc-tools --pre
>>> Node,js:
>>>
>>> npm install grpc
>>>
>>> npm install grpc-tools
>>> PHP:
>>>
>>> [sudo] pecl install grpc
>>>
>>> gem install ronn rake
>>>
>>> git clone https://github.com/stanley-cheung/Protobuf-PHP
>>>
>>> cd Protobuf-PHP
>>>
>>> rake pear:package version=1.0
>>>
>>> [sudo] pear install Protobuf-1.0.tgz
>>> C#:
>>>
>>>    -
>>>
>>>    Open Visual Studio / MonoDevelop / Xamarin Studio and start a new
>>>    project/solution.
>>>    -
>>>
>>>    Add the Grpc NuGet package as a dependency (Project options ->
>>>    Manage NuGet Packages).
>>>    -
>>>
>>>    To be able to generate code from Protocol Buffer (.proto) file
>>>    definitions, add the Grpc.Tools NuGet package that contains Protocol
>>>    Buffers compiler (protoc) and the gRPC protoc plugin.
>>>    -
>>>
>>>    Make sure to “show prerelease packages”.
>>>
>>> Java:
>>>
>>> Released on Maven central, might take a few hours to appear.
>>> Objective-C:
>>>
>>> Cocoapod spec and instructions
>>> <https://github.com/grpc/grpc/tree/master/src/objective-c>.
>>>
>>> Notes for Development Release 1.0.0-pre1
>>>
>>> Release 1.0.0-pre1 for Java
>>> <https://github.com/grpc/grpc-java/releases/tag/v1.0.0-pre1>
>>> Release 1.0.0-pre1
>>>
>>>
>>> Please see the notes for the previous releases here:
>>> https://github.com/grpc/grpc/releases
>>>
>>> Development release of github.com/grpc/grpc.
>>> C-core:
>>>
>>>    -
>>>
>>>    Performance boost using delayed writes.
>>>    -
>>>
>>>    Added support for SO_REUSEPORT.
>>>    -
>>>
>>>    New error propagation system.
>>>    -
>>>
>>>    Default log verbosity is now ERROR.
>>>    -
>>>
>>>    Various optimizations and fixes.
>>>
>>> Python:
>>>
>>>    -
>>>
>>>    Made handlers optional in grpc.server
>>>    <https://github.com/grpc/grpc/pull/7160>.
>>>    -
>>>
>>>    Beta support for Python 3 on Mac OS X x64, Windows x86, and Linux
>>>    x86 and x64.
>>>    -
>>>
>>>    Added a reference implementation of server health-checking as the
>>>    package grpcio-health-checking.
>>>    -
>>>
>>>    Added distutils custom command for gRPC proto generation to
>>>    grpcio-tools.
>>>    -
>>>
>>>    Many behind-the-scenes fixes.
>>>
>>> Ruby:
>>>
>>>    -
>>>
>>>    Removed Core::CompletionQueue from the public API. Removed all
>>>    function parameters that required CompletionQueues.
>>>    -
>>>
>>>    Split trailing metadata out into a separate instance variable on
>>>    calls.
>>>
>>> PHP:
>>>
>>>    -
>>>
>>>    Fixed shutdown hang #4017.
>>>    -
>>>
>>>    PHP7 support #7464.
>>>
>>> C#:
>>>
>>>    -
>>>
>>>    Support for use of the Grpc nuget package with dotnet CLI tooling
>>>    #7230.
>>>
>>> Objective-c:
>>>
>>>    -
>>>
>>>    https://github.com/grpc/grpc/pull/7264 BoringSSL's podspec (as v5.0)
>>>    now builds correctly for devices (not only simulator).
>>>    -
>>>
>>>    https://github.com/grpc/grpc/pull/7288 Well-known protos ([the
>>>    `.proto` files distributed with `protoc`](https://github.com/
>>>    google/protobuf/tree/master/src/google/protobuf
>>>    <https://github.com/google/protobuf/tree/master/src/google/protobuf>))
>>>    can now be used when compiling pods as dynamic frameworks.
>>>    -
>>>
>>>    https://github.com/grpc/grpc/pull/7359 `protoc` and the gRPC plugin
>>>    for Objective-C are now distributed as pods, so versions mismatches among
>>>    them and the Protobuf and gRPC runtimes are an issue of the past.
>>>    -
>>>
>>>    https://github.com/grpc/grpc/pull/6855 Support for multiple services
>>>    defined in the same `.proto` file.
>>>    -
>>>
>>>    (Various pull requests) Compressed data and connectivity changes are
>>>    now handled more robustly.
>>>    -
>>>
>>>    https://github.com/grpc/grpc/pull/6849 gRPC can now be integrated as
>>>    dynamic frameworks (`use_frameworks!` in your `Podfile`), which means it
>>>    can be used alongside pods written in Swift.
>>>
>>> Node.js:
>>>
>>>    -
>>>
>>>    Split node health check code into a separate package:
>>>    grpc-health-check.
>>>
>>>
>>>
>>>
>>> --
> 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 [email protected].
> To post to this group, send email to [email protected].
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/grpc-io/CALLuE_mstLb4mSCpUDv870peE7nh52G4Kvcj
> 7HVKmpBXYigKsw%40mail.gmail.com
> <https://groups.google.com/d/msgid/grpc-io/CALLuE_mstLb4mSCpUDv870peE7nh52G4Kvcj7HVKmpBXYigKsw%40mail.gmail.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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/CAOWnRi-Vnjxb2Bnzxm_qTrvgk7XTRcjLEoccgsrjUcxwKPncpg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to