Bug 1592523 - .NET Core Runtime 2.1.1 and SDK 2.1.301
Summary: .NET Core Runtime 2.1.1 and SDK 2.1.301
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: dotNET
Classification: Red Hat
Component: rh-dotnet21
Version: 2.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ga
: 2.0
Assignee: Omair Majid
QA Contact: Radka Gustavsson
Toby Drake
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-18 18:33 UTC by Omair Majid
Modified: 2018-06-25 07:02 UTC (History)
4 users (show)

Fixed In Version: rh-dotnet21-dotnet-2.1.301-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-06-25 07:02:12 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:1966 0 None None None 2018-06-25 07:02:40 UTC

Description Omair Majid 2018-06-18 18:33:48 UTC
The .NET Core 2.1.1 is scheduled to go out soon: 
https://twitter.com/DamianEdwards/status/1007071527320240129

We need to build the corresponding version of .NET Core from source-build and ship that for Red Hat Enterprise Linux.

Comment 1 Toby Drake 2018-06-18 18:38:34 UTC
Will updates need to be made to the .NET Core 2.1 documentation?

Comment 2 Omair Majid 2018-06-18 18:58:17 UTC
(In reply to tdrake from comment #1)
> Will updates need to be made to the .NET Core 2.1 documentation?

I doubt it. Maybe some known issues get fixed, but it's a small conservative update that shouldn't bring in any huge changes. We will know more once we play around with the final bits.

Comment 6 errata-xmlrpc 2018-06-25 07:02:12 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:1966


Note You need to log in before you can comment on or make changes to this bug.