Bug 465264 – Release begins with 0 for non-prelease tomcat version

Bug 465264 - Release begins with 0 for non-prelease tomcat version

Summary:	Release begins with 0 for non-prelease tomcat version

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	tomcat5 (Show other bugs)
Sub Component:
Version:	9
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	David Walluck
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2008-10-02 10:04 EDT by Andrew Overholt
Modified:	2008-10-30 13:18 EDT (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2008-10-30 10:46:20 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Andrew Overholt 2008-10-02 10:04:21 EDT

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 10:46:20 EDT

This is fixed.

Comment 2 David Walluck 2008-10-30 12:02:43 EDT

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 12:34:40 EDT

Let's get spot to clarify.

Comment 4 Tom "spot" Callaway 2008-10-30 13:18:34 EDT

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.

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