Bug 1542031

Summary:	ocaml-result-1.3 is available
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	ocaml-result	Assignee:	Ben Rosser <rosser.bjr>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	rosser.bjr
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-05-21 22:56:09 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 2018-02-05 12:30:45 UTC

Latest upstream release: 1.3
Current version/release in rawhide: 1.2-3.fc28
URL: https://github.com/janestreet/result

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/16706/

Comment 1 Ben Rosser 2018-05-21 22:56:09 UTC

So... I'm going to close this as WONTFIX.

ocaml-result is basically just a typedef (on sufficiently new OCaml). As far as I can tell all that changed between 1.2 and 1.3 is that they switched to using jbuilder/dune to compile ocaml-result, which personally feels a bit absurd-- at best-- for a package that's just a type declaration.

I might be wrong to do this. If so, someone should please reopen this ticket or file a new one. But for now I don't see a compelling reason to ever "update" to "1.3" when the source itself is unchanged.