Bug 1703495

Summary:	R-3.6.0 is available
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	R	Assignee:	Tom "spot" Callaway <tcallawa>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	alphaomega, itsme_410, quantum.analyst, tcallawa
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	R-3.6.0-1.fc30 R-3.6.1-2.fc29	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-16 01:09:16 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Upstream Release Monitoring 2019-04-26 15:13:44 UTC

Latest upstream release: 3.6.0
Current version/release in rawhide: 3.5.3-1.fc31
URL: https://www.r-project.org/

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring

Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.

Based on the information from anitya:  https://release-monitoring.org/project/4150/

Comment 1 Fedora Update System 2019-06-12 23:39:25 UTC

FEDORA-2019-f4070ead29 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-f4070ead29

Comment 2 Fedora Update System 2019-06-12 23:39:34 UTC

FEDORA-2019-5fe2ddffa0 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-5fe2ddffa0

Comment 3 Elliott Sales de Andrade 2019-06-13 01:37:24 UTC

*** Bug 1714068 has been marked as a duplicate of this bug. ***

Comment 4 Fedora Update System 2019-06-16 01:09:16 UTC

R-3.6.0-1.fc30, lapack-3.8.0-12.fc30, rkward-0.7.0-7.fc30, rpy-3.0.4-2.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.

Comment 5 Fedora Update System 2019-08-30 03:50:19 UTC

FEDORA-2019-32499f9021 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-32499f9021

Comment 6 Fedora Update System 2019-08-30 15:41:20 UTC

R-3.6.1-1.fc29, R-rpm-macros-1.1.0-2.fc29, rkward-0.7.0-9.fc29, rpy-2.9.5-4.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-32499f9021

Comment 7 Ranjan Maitra 2019-08-30 17:43:48 UTC

I believe that we need an update for F30.

Comment 8 Fedora Update System 2019-09-01 02:20:02 UTC

FEDORA-2019-32499f9021 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-32499f9021

Comment 9 Fedora Update System 2019-09-02 01:49:02 UTC

R-3.6.1-2.fc29, rkward-0.7.0-9.fc29, rpy-2.9.5-4.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-32499f9021

Comment 10 Fedora Update System 2019-09-29 02:22:26 UTC

R-3.6.1-2.fc29, rkward-0.7.0-9.fc29, rpy-2.9.5-4.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.