Bug 843031

Summary:	RFE: Make --fetch-pubsnum the default for publish
Product:	[Community] PressGang CCMS	Reporter:	Joshua Wulf <jwulf>
Component:	CSProcessor	Assignee:	Lee Newson <lnewson>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	1.x	CC:	jwulf, lcarlon, mcaspers
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-09-20 09:53:14 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Joshua Wulf 2012-07-25 11:34:49 UTC

Rationale:

1. Fetching the latest pubsnumber can never result in a wrong outcome.
2. 99% of the time it will in fact actively save the author from the hell of manually syncing pubsnumbers.
3. The overhead of fetching the latest pubsnumber as a percentage of the whole process is a micro portion of 1% (downloading topics, pushing to brew etc...).
4. Typing --fetch-pubsnum every time is 80% more work.

Comment 1 Lee Newson 2012-07-27 07:18:58 UTC

Point one is incorrect actually, if the --fetch-pubsnum is specified then it will fail if the URL doesn't exist. Other then that the only argument I have against it is that not all builds might be published using brew.

It was for those two reasons that I didn't make it the default in the first place (as I've mentioned in Bug #829947 already). Anyways I'll re-evaluate it and talk it over and get back to this RFE.

Comment 2 Lee Newson 2012-09-20 09:53:14 UTC

Since the pubsnumber is no longer valid in Publican 3, this functionality is no longer usable and therefore would be a waste of time. So I'm marking this as closed.