[6071] in Release_7.7_team

home help back first fref pref prev next nref lref last post

I think some Athena 10 issues belong in IS&T Jira.

daemon@ATHENA.MIT.EDU (William Cattey)
Fri Oct 24 18:55:43 2008

Mime-Version: 1.0 (Apple Message framework v753.1)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <2B002BC5-318B-461F-BC28-BD2C0CFE6B20@mit.edu>
Content-Transfer-Encoding: 7bit
From: William Cattey <wdc@MIT.EDU>
Date: Fri, 24 Oct 2008 18:54:49 -0400
To: release-team@mit.edu
X-Spam-Flag: NO
X-Spam-Score: 0.00

When I asked a couple months ago where to track Athena 10 issues,  
Greg Hudson pointed me at the debathena issue tracker, and suggested  
that should be sufficient.

I've had some experience using that tracker, and I'm coming to  
believe that maybe we need a separate tracker.
Here's my thinking:

The debathena trac system used by the debathena folk is a broad  
inventory of issues relating to many versions and many different  
approaches to using and developing debathena.  In the course of  
testing Athena 10, Alex Prengel, Jonathan Reed, and I have all found  
issues that relate specifically to the Athena 10 product as it would  
either be deployed to Athena Clusters, or how it would be used by  
individuals familiar with Athena 9.

Examples:

	Vagaries of the migration from LPRng to CUPS and its impact on 3rd  
party software.
	The names of the different sessions on offer from the Athena 10  
Xlogin greeter screen.

There is actually an Athena10 Jira setup that was created before I  
got serious about issue tracking:
https://jira.mit.edu/jira/browse/ATN

I want to use Jira's ability to tie issues to a particular release,  
and to a calendar so that the various issues we see get resolved as  
Athena 10 rolls out.

I think I'm going to start an inventory of issues there, beginning  
with what remains of Alex Prengel's printing issues, and the  
debathena issues that I've previously labeled as "wdc-blocker".

Do people have strong feelings pro or con on my proposed course of  
action?

-Bill

----
Important: IS&T IT staff will *NEVER* ask you for your password, nor  
will MIT send you email requesting your password information. Please  
continue to ignore any email messages that claim to require you to  
provide such information.
----

William Cattey
Linux Platform Coordinator
MIT Information Services & Technology

N42-040M, 617-253-0140, wdc@mit.edu
http://web.mit.edu/wdc/www/




home help back first fref pref prev next nref lref last post