[rhelv6-list] dhclient running TWICE during boot (RHEL 6.2)

[Grzegorz Witkowski]

I also got confused. With a support there is a SLA and engineer would often
open a bugzilla with no SLA.
Logically then SLA is negated. Am I missing something?
Basically that also gives an impression that as long as there is no case
open by supported customer RH does not really bother if there is a problem
reported by community. Maybe it should be reported back to Fedora to get it
fixed there first and then maybe it'll make through to RHEL?
On May 8, 2012 4:41 p.m., "thomas at redhat.com" <thomas at redhat.com> wrote:

> On 05/07/2012 12:50 PM, Paul Smith wrote:
>
>> I think I'm misunderstanding something about Red Hat support and
>> Bugzilla.  How does one actually get bugs fixed?  It seems like they are
>> ignored until the next beta is started, then you get a message for each
>> one saying "sorry, this bug is still unresolved so it has been
>> rejected".  Is this some new variant of Agile I'm not familiar with?  I
>> never heard of a development process where you just reject all the open
>> bugs you didn't have time to fix when you started beta... what a
>> concept!  I think we should start doing that at my company too.  It
>> would really improve our QA metrics, that's for sure.
>>
>> Am I just supposed to keep filing the bug again for each new release?
>> This seems somewhat Sisyphean, even for open source.
>>
>
> There is a very important distinction between opening a support ticket and
> opening a bugzilla ticket.
>
> With support, there is an SLA. With support, our engineers will often open
> a bugzilla. But there is no SLA for BZ.
>
> Can you point me to an example of a bug that got closed as you describe?
>
>
> --
> Thomas Cameron, RHCA, RHCSS, RHCDS, RHCVA, RHCX
> Chief Architect, Canada and Central US
> 512-241-0774 office / 512-585-5631 cell
> http://people.redhat.com/**tcameron/ <http://people.redhat.com/tcameron/>
> IRC: choirboy / AIM: rhelguy / Yahoo: rhce_guy /Google+
> http://ongpl.us/tdc
>
> ______________________________**_________________
> rhelv6-list mailing list
> rhelv6-list at redhat.com
> https://www.redhat.com/**mailman/listinfo/rhelv6-list<https://www.redhat.com/mailman/listinfo/rhelv6-list>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/rhelv6-list/attachments/20120508/b319687d/attachment.htm>