Bug 465264

Summary:	Release begins with 0 for non-prelease tomcat version
Product:	[Fedora] Fedora	Reporter:	Andrew Overholt <overholt>
Component:	tomcat5	Assignee:	David Walluck <dwalluck>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	9	CC:	devrim, tcallawa
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-10-30 14:46:20 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 Andrew Overholt 2008-10-02 14:04:21 UTC

Why is the release 0.<something involving jpp> when 5.5.27 doesn't appear to be a pre-release on tomcat's website?

Comment 1 Andrew Overholt 2008-10-30 14:46:20 UTC

This is fixed.

Comment 2 David Walluck 2008-10-30 16:02:43 UTC

Does the policy really say that 0 can only be used for prereleases? Anyway, it might not be an upstream tomcat prerelease version, but it was an upstream JPackage prerelease version at the time.

Comment 3 Andrew Overholt 2008-10-30 16:34:40 UTC

Let's get spot to clarify.

Comment 4 Tom "spot" Callaway 2008-10-30 17:18:34 UTC

You really should try to reserve the 0 for prereleases. If you had some overwhelmingly compelling reason to use it, then I'd probably let it slide, but it is important to try to keep rpm package ordering as sane as possible.