All,

Would it be possible to put the SSG release schedule on a regular basis?

I.e. you'll get a new release every 2 months unless there is a critical fix?

That way there's some consistency in when people should expect to find updates.

I'm definitely not criticizing, just trying to make things easier for maintenance shops to pick up. Many groups get hit with whatever their local security team picks up, whenever they pick it up. If it's on a regular schedule, then they can proactively incorporate it into their maintenance scheduling.

Thanks!

Trevor


On Fri, May 9, 2014 at 10:16 AM, Jan Lieskovsky <jlieskov@redhat.com> wrote:
Hello folks,

  it has been three months again from the last SCAP Security Guide
0.1-16 release (last was Fri, 21-th Feb of 2014). In between 76 changes
/ patches were applied:

  $ git log --format=%h --since="21-Feb-2014" | wc -l
  76

  So I think it's time to make a new official release (for those people
relying on RPM packages instead of building directly from Git).

  Besides that the count of patches (diff 0.1-16 vs current git) makes
the maintenance cost of 0.1-16 tarball + set of patches to be applied
above it (for example due to package source tarball hash check) very high.

  Therefore proposing to make a new 0.1.17 release. The attached
patch updates the spec & if approved new upstream source tarball &
new EPEL package release would follow.

Please review.

Thank you && Regards, Jan.
--
Jan iankko Lieskovsky / Red Hat Security Technologies Team

_______________________________________________
scap-security-guide mailing list
scap-security-guide@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide




--
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699
tvaughan@onyxpoint.com

-- This account not approved for unencrypted proprietary information --