[CentOS-devel] announcing content from the sign process

[Karanbir Singh]

On 26/11/15 10:40, Karanbir Singh wrote:
> the release id is : CSIG-2015:XXXX to match the format of what we are
> already doing in centos-announce. Here the XXXX will be a serial
> starting from 0001 and will run through the calendar year.

one problem with this, is that RedHat already allocates numbers in
exactly the same manner, ie. were going to conflict on ID's unless
everyone always uses the entire id (ie. use CSIG-2015:0001 instead of
2015:0001 ).

One way to fix this might be to add an alpha digit in the second part,
eg: CSIG-2015:A001 that keeps the component id part ( 2015:A001 )
unique and usable as the ID.

> There will be one post per day per sig, ie. if there are multiple SRPMS
> included in the push, they will be summarised into one email. This is a
> change from how we do the distro updates, where there is an email per
> srpm ( with a few exceptions, but very few ). Open to change requests on
> this.

One slight complication is that the CentOS Linux 6 and 7 content is
marked differently so that people can filter on it with the
centos-announce list's filtering option. We got lucky today in that the
Cloud SIG only had CentOS Linux 7 content, and virt sig only has CentOS
Linux 6 content.

The options we have is : keep posting one per CentOS Linux release, per
SIG per day. or Mash the different CentOS Linux releases updates into
one email per SIG, this would make it easier to parse for people
tracking multiple versions, but would break filters in the announce list
for people who only want one release versions content.

thoughts ?



-- 
Karanbir Singh
+44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
GnuPG Key : http://www.karan.org/publickey.asc