[FACT-1425] Facter 3.1.7 incorrectly identifies itself as version 3.2.0 Created: 2016/05/19  Updated: 2016/07/25  Resolved: 2016/06/12

Status: Closed
Project: Facter
Component/s: Community
Affects Version/s: FACT 3.1.7
Fix Version/s: FACT 3.3.0

Type: Bug Priority: Normal
Reporter: Christoph Schug Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Release Notes: Bug Fix
Release Notes Summary: Docs folks: this is going to require a bit of a special comment. Perhaps something like this:

Facter 3.1.7 and 3.1.8 both incorrectly identified themselves as Facter 3.2.0 - both with {{facter --version}} and with {{facter facterversion}}.

To avoid adding to the confusion, facter will skip a facter 3.2.0 version - the next release will be (and will report itself as) facter 3.3.0.

 Description   

Facter 3.1.7 incorrectly identifies itself as version 3.2.0.

Code build from the 3.1.7 release tarball on Github, facter-3.1.7.tar.gz (SHA256 ebb703068daaf6ff880be8d14898709ccea44288874450e25a887ecb0a5e04ae)

$ facter facterversion
3.2.0



 Comments   
Comment by Christoph Schug [ 2016/06/01 ]

Same with Facter 3.1.8. I'm wondering if there aren't any most basic tests when preparing for a release.

Comment by Kylo Ginsberg [ 2016/06/08 ]

Christoph Schug yeah we just internalized this last week, unfortunately shortly after 3.1.8 was tagged. So, two things:

  • as a corrective action going forward, we're scrubbing our release sanity checks to catch this (/cc Rob Braden).
  • meanwhile, here in tickets.puppet.com, we're essentially skipping 3.2.0. So the next release will be (and report itself as!) facter 3.3.
Generated at Mon Dec 09 07:45:11 PST 2019 using JIRA 7.7.1#77002-sha1:e75ca93d5574d9409c0630b81c894d9065296414.