Bug 465264 - Release begins with 0 for non-prelease tomcat version
Summary: Release begins with 0 for non-prelease tomcat version
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: tomcat5
Version: 9
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: David Walluck
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-10-02 14:04 UTC by Andrew Overholt
Modified: 2008-10-30 17:18 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-10-30 14:46:20 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.