[torquedev] torque bugzilla

Glen Beane glen.beane at gmail.com
Mon Feb 9 13:16:42 MST 2009


thanks for the update

On Mon, Feb 9, 2009 at 3:16 PM, Josh Butikofer
<josh at clusterresources.com> wrote:
> Everyone,
>
> Just a follow-up on the TORQUE Bugzilla upgrade. I spoke with our IT
> department, which is doing the upgrade of Bugzilla, and due to increased
> workload and timelines they have not yet upgraded Bugzilla. I've petitioned
> for some of their time to help speed this along, but they've told me it will
> have to wait for later this month.
>
> I'm sorry for delay. :P
>
> Josh Butikofer
> Cluster Resources, Inc.
> #############################
>
>
> Josh Butikofer wrote:
>>
>> After having a pow-wow here, we agree that "scrubbing" or resetting the
>> Bugzilla found at http://www.clusterresources.com/bugzilla/ and using it
>> for TORQUE is the best idea. When a TORQUE user encounters a bug or has
>> a feature request that they want the community to see, they can post it
>> on Bugzilla or the mailing list. If the problem in the mailing list
>> looks like it should be in Bugzilla, then it can be added there as well
>> to track its progress.
>>
>> It has been requested that CRI also post all internal bugs to Bugzilla.
>> For many of the bug reports we receive, this would probably work if we
>> abstract the bug to non-specifics. For example, if site ACME reports
>> that nodes A, B, and C are going down when user "joe" submits a job, we
>> can then create a bug report in Bugzilla that says something like
>> "customers have reported that nodes go down when a specific user submits
>> a job."
>>
>> We have to make it generic because we have an obligation to our
>> customers to protect their privacy--mostly due to security concerns.
>> This is mostly something that CRI will work out, but we find it in
>> everyone's best interest if we make it publicly known when there are
>> problems/bugs in TORQUE. This has always been our policy and we haven't
>> purposely tried to hide things from the community.
>>
>> Josh Butikofer
>> Cluster Resources, Inc.
>> #############################
>
> _______________________________________________
> torquedev mailing list
> torquedev at supercluster.org
> http://www.supercluster.org/mailman/listinfo/torquedev
>


More information about the torquedev mailing list