[6493] in Release_7.7_team
Re: Meet this Friday or next Friday?
daemon@ATHENA.MIT.EDU (Oliver Thomas)
Wed Nov 4 10:21:18 2009
From: "Oliver Thomas" <othomas@MIT.EDU>
To: "jdreed@mit.edu" <jdreed@mit.edu>
CC: "release-team@mit.edu" <release-team@mit.edu>
Date: Wed, 4 Nov 2009 10:21:04 -0500
Message-ID: <281F4838-CE0B-4AA2-95DB-88B59027C8F4@exchange.mit.edu>
In-Reply-To: <4C945BE9-F6B5-4E57-931E-913040A223F7@mit.edu>
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
X-Spam-Flag: NO
X-Spam-Score: 0.00
Content-Transfer-Encoding: 8bit
Hi Jon,
Either Friday will work for me.
I can try to get some summary info around on what would be helpful to
us to capture on the release projects. Daptiv can mainly stay behind
the scenes at this point, but for our purposes we're just talking
about consistent project info we need to capture so we can look at
them and prioritize the pieces in the same context as other projects,
assess impact of not doing certain things, and so on. The template
isn't too bad.
Oliver
--
Oliver Thomas
Information Services and Technology
Massachusetts Institute of Technology
+1 617 253 9682
+1 617 835 9682 /m
othomas@mit.edu
On Nov 4, 2009, at 9:23 AM, Jonathan Reed wrote:
> Aside from our regular updates, one of the big things I'd like to do
> at the next release-team is to discuss how we can reframe each new
> Ubuntu Release as an IS&T Project(tm) (ie: something that goes in
> Daptiv). I think that will help us get a better handle on resources
> needed for each upcoming release.
>
> It seems fairly evident that Karmic, with it's dropping of krb4 and
> it's rewrite of gdm, is likely to be the exception rather than the
> rule, and as such, I think it's best that we try and articulate just
> how much effort we expect to be needed for future releases. I have
> several ideas on how we can do this, particularly by looking at our
> Jaunty release, and dividing the tasks into the following categories:
> - ensuring existing core Athena components work on the new release
> - work due to changes in the MIT environment (i.e. Exchange)
> - adding new features requested by IS&T (i.e. metrics)
> - adding new features requested by the general community
> - bugfixes
>
> Once we have that information, we can perform the same task for
> Karmic, and then we'll be in a good place to know what future releases
> are like. It's important to separate the chroot work and the Exchange
> work from the task of "Making Debathena work on Jaunty", because those
> two tasks are unlikely to be repeated for future releases. That way
> we can be in a good position to say "It should take X days to get
> Debathena working on Lucid, X+Y days if Lucid switches from GNOME to
> KDE, X+Z days if the cluster machines are switched from Dells to XO
> laptops, etc."
>
> That having been said, Evan noted he can't make this week's meeting,
> and I think that in order to have the discussion above, it's important
> that Evan, Geoff, Andrew and Bob be present. So, can we bump this
> weeks' meeting and shift the schedule so that we meet a week from
> Friday? (I now realize that's Friday the 13th, but whatever). I am
> open to meeting at other days/times too, but we should definitely get
> this done either this week or next week.
>
> Thoughts?
>
> -Jon
