[CentOS] What happened to 6.1

[m.roth at 5-cent.us]

Johnny Hughes wrote:
> On 10/21/2011 10:01 AM, Les Mikesell wrote:
>> On Fri, Oct 21, 2011 at 9:51 AM, Nicolas Thierry-Mieg
>> <Nicolas.Thierry-Mieg at imag.fr> wrote:
>>
>>>> Johnny, chill. I don't blame him for being confused. Up until right
>>>> now, you updated to a point release, then, over the weeks and months,
>>>> there were updates. All of a sudden, there are *no* updates for the 6.0
>>>> point release, which is a major change in what everyone expected,
>>>> based on history.
>>>
>>> this is the way it has always been: once upstream releases x.y+1 ,
>>> there are no more updates to x.y (in upstream and therefore also in
>>> centos), until centos releases x.y+1 .
>>
>> Yes, but that used to be transparent, because the centos x.y+1 release
>> happened quickly so it didn't matter that the update repo was held
>> back until an iso build was done.
<snip>
> Now, for version 6, they have:
>
> Red Hat Enterprise Linux Server (v. 6)
> Red Hat Enterprise Linux Workstation (v. 6)
> Red Hat Enterprise Linux Desktop (v. 6)
> Red Hat Enterprise Linux HPC Node (v. 6)
> Red Hat Enterprise Linux Workstation FasTrack (v. 6)
> Red Hat Enterprise Linux Server FasTrack (v. 6)
> Red Hat Enterprise Linux Desktop FasTrack (v. 6)
> Red Hat Enterprise Linux Scalable File System (v. 6)
> Red Hat Enterprise Linux Resilient Storage (v. 6)
> Red Hat Enterprise Linux Load Balancer (v. 6)
> Red Hat Enterprise Linux HPC Node FasTrack (v. 6)
> Red Hat Enterprise Linux High Performance Network (v. 6)
> Red Hat Enterprise Virtualization
>
> They have the same install groups with different packages based on the
> above groupings, so we have to do some kind of custom generation of the
> comps files to things work.

Wait, are you saying that a given install group name installs different
packages, depending on the release name? I mean, if I were working on the
team, I'd build an Everything release group, and just have subsets, based
on which release group was chosen.

And what's the FasTrack, as opposed to the non-FasTrack?

      mark