Should removed classes become Undeclared?

> "Dan Ingalls" <[hidden email]> wrote:
> <snip>
>> I regret that I don't have time to fix these right now.  However, if
>> there is a well-intentioned soul out there, he or she will perhaps
>> find the method below to be quite useful.  It found 165 methods in my
>> system with this pattern.
>
> I'll do it, in my (virgin) 3.9a-6721.
>
> frank
>

> Er, when I make these MCDs (mark the repository as storing diffs,  
> hit the
> Save button) my image (3.9a-6721) pops up a never-ending sequence of
> "Diffing..." messages, but never seems to stop. I mean, I'm trying  
> to save
> the Collections mcd, which altered about 10 or so methods, and the  
> saving
> process has already taken 7 minutes! Am I doing something crazily  
> wrong?
>
> My previous attempt was on the Traits package, and that took at  
> least an
> hour before I gave up.
>
> Is there a way to split up a ChangeSet into a set of per-package  
> change
> sets? Then I can post those to Mantis instead of MCDs.
>
> frank
>
>

> This is really strange.
> I do not have time now to check but we will.
>
> Stef
>
>
>> Er, when I make these MCDs (mark the repository as storing diffs,  
>> hit the
>> Save button) my image (3.9a-6721) pops up a never-ending sequence of
>> "Diffing..." messages, but never seems to stop. I mean, I'm trying  
>> to save
>> the Collections mcd, which altered about 10 or so methods, and the  
>> saving
>> process has already taken 7 minutes! Am I doing something crazily  
>> wrong?
>>
>> My previous attempt was on the Traits package, and that took at  
>> least an
>> hour before I gave up.
>>
>> Is there a way to split up a ChangeSet into a set of per-package  
>> change
>> sets? Then I can post those to Mantis instead of MCDs.
>>
>> frank
>>
>>
>
>

> This is really strange.
> I do not have time now to check but we will.
>
> Stef
>
>
>> Er, when I make these MCDs (mark the repository as storing diffs,
>> hit the
>> Save button) my image (3.9a-6721) pops up a never-ending sequence of
>> "Diffing..." messages, but never seems to stop. I mean, I'm trying
>> to save
>> the Collections mcd, which altered about 10 or so methods, and the
>> saving
>> process has already taken 7 minutes! Am I doing something crazily
>> wrong?
>>
>> My previous attempt was on the Traits package, and that took at
>> least an
>> hour before I gave up.
>>
>> Is there a way to split up a ChangeSet into a set of per-package
>> change
>> sets? Then I can post those to Mantis instead of MCDs.
>>
>> frank
>>
>>
>
>

> As per Adrian's suggestion I've uploaded all the MCZs to the Mantis  
> bug
> report (http://bugs.impara.de/view.php?id=2788) - except for  
> Morphic. The
> Upload File section quotes a maximum file size of 2,000k, and  
> Morphic-fbs.66
> is 1,084,635 bytes, yet Mantis complains that that file's too  
> large. Could
> it be that the maximum file size is actually 1000K? The next-
> largest file I
> uploaded was 792K.
>
> Any suggestions how to get the Morphic file up? I'd love to make an  
> MCD from
> Morphic-fbs.66 and Morphic-md.65, for instance. Ooh, hang on! I see a
> Morphic-fbs.66(md.65).mcd file in my package-cache! OK, I've  
> uploaded that
> to the bug report. Hopefully that'll work for propogating my changes.
>
> frank
>
> ----- Original Message -----
> From: "Adrian Lienhard" <[hidden email]>
> To: "The general-purpose Squeak developers list"
> <[hidden email]>
> Sent: Tuesday, February 14, 2006 12:17 PM
> Subject: Re: Use of == for arithmetic equality
>
>
> Hi Frank,
>
> I suggest to just use MCZ (no diffing). Monticello nicely deals with
> merging different versions (compared to changesets vs fileOuts).
>
> Adrian
>
> On Feb 14, 2006, at 11:12 , stéphane ducasse wrote:
>
>> This is really strange.
>> I do not have time now to check but we will.
>>
>> Stef
>>
>>
>>> Er, when I make these MCDs (mark the repository as storing diffs,
>>> hit the
>>> Save button) my image (3.9a-6721) pops up a never-ending sequence of
>>> "Diffing..." messages, but never seems to stop. I mean, I'm trying
>>> to save
>>> the Collections mcd, which altered about 10 or so methods, and the
>>> saving
>>> process has already taken 7 minutes! Am I doing something crazily
>>> wrong?
>>>
>>> My previous attempt was on the Traits package, and that took at
>>> least an
>>> hour before I gave up.
>>>
>>> Is there a way to split up a ChangeSet into a set of per-package
>>> change
>>> sets? Then I can post those to Mantis instead of MCDs.
>>>
>>> frank
>>>
>>>
>>
>>
>
>
>

> As per Adrian's suggestion I've uploaded all the MCZs to the Mantis
> bug
> report (http://bugs.impara.de/view.php?id=2788) - except for
> Morphic. The
> Upload File section quotes a maximum file size of 2,000k, and
> Morphic-fbs.66
> is 1,084,635 bytes, yet Mantis complains that that file's too
> large. Could
> it be that the maximum file size is actually 1000K? The next-
> largest file I
> uploaded was 792K.
>
> Any suggestions how to get the Morphic file up? I'd love to make an
> MCD from
> Morphic-fbs.66 and Morphic-md.65, for instance. Ooh, hang on! I see a
> Morphic-fbs.66(md.65).mcd file in my package-cache! OK, I've
> uploaded that
> to the bug report. Hopefully that'll work for propogating my changes.
>
> frank
>
> ----- Original Message -----
> From: "Adrian Lienhard" <[hidden email]>
> To: "The general-purpose Squeak developers list"
> <[hidden email]>
> Sent: Tuesday, February 14, 2006 12:17 PM
> Subject: Re: Use of == for arithmetic equality
>
>
> Hi Frank,
>
> I suggest to just use MCZ (no diffing). Monticello nicely deals with
> merging different versions (compared to changesets vs fileOuts).
>
> Adrian
>
> On Feb 14, 2006, at 11:12 , stéphane ducasse wrote:
>
>> This is really strange.
>> I do not have time now to check but we will.
>>
>> Stef
>>
>>
>>> Er, when I make these MCDs (mark the repository as storing diffs,
>>> hit the
>>> Save button) my image (3.9a-6721) pops up a never-ending sequence of
>>> "Diffing..." messages, but never seems to stop. I mean, I'm trying
>>> to save
>>> the Collections mcd, which altered about 10 or so methods, and the
>>> saving
>>> process has already taken 7 minutes! Am I doing something crazily
>>> wrong?
>>>
>>> My previous attempt was on the Traits package, and that took at
>>> least an
>>> hour before I gave up.
>>>
>>> Is there a way to split up a ChangeSet into a set of per-package
>>> change
>>> sets? Then I can post those to Mantis instead of MCDs.
>>>
>>> frank
>>>
>>>
>>
>>
>
>
>

> On 2/14/06, Frank Shearar <[hidden email]> wrote:
>> Ah, OK. I thought that fixes were supposed to go to Mantis first,  
>> then to
>> inbox after the fixes had been vetted. I'm sorry if I've made more  
>> work for
>> everyone!
>>
> Yes, you're right. And Bert isn't ;-). Package teams should be the
> only ones that publish to the integration inbox, because they are the
> ones that decide whether a package version is integration-ready or
> not. So putting them on Mantis is the correct action (Mantis is in
> effect the inbox of the package teams).
>
>

> On 2/14/06, Frank Shearar <[hidden email]> wrote:
>> Ah, OK. I thought that fixes were supposed to go to Mantis first,  
>> then to
>> inbox after the fixes had been vetted. I'm sorry if I've made more  
>> work for
>> everyone!
>>
> Yes, you're right. And Bert isn't ;-). Package teams should be the
> only ones that publish to the integration inbox, because they are the
> ones that decide whether a package version is integration-ready or
> not. So putting them on Mantis is the correct action (Mantis is in
> effect the inbox of the package teams).

> "Cees De Groot" <[hidden email]> wrote:
>
>> On 2/14/06, Bert Freudenberg <[hidden email]> wrote:
>>> Also, I'd prefer directly publishing to a MC repository rather than
>>> uploading to Mantis.
>>>
>> Absolutely. I'd publish that sort of stuff in my own repository in
>> such a case and add pointers to Mantis.
>
> Er, so should I save the in-image package MCZs to the inbox  
> repository? Or
> will whoever manages the inbox grab the MCZs from the Mantis bug  
> report?
>
> frank
>
>
>

> On 2/14/06, Frank Shearar <[hidden email]> wrote:
>> Er, so should I save the in-image package MCZs to the inbox  
>> repository? Or
>> will whoever manages the inbox grab the MCZs from the Mantis bug  
>> report?
>>
> Neither. The regular flow is community -> mantis -> package team ->
> inbox -> release team. In that way, we ensure that the package team
> controls what is released and when, plus that they don't need to look
> left and right for inbound stuff. And it keeps the inbox clean (which
> helps the release team in evaluating how much stuff is available
> there).
>
> It's all a bit harder with this new system for cross-cutting patches,
> but that's the trade-off we made when moving to the team model (and,
> with it, giving the team ultimate responsibility for what is released
> - responsibility and control go hand in hand here, as they should)

> "Cees De Groot" <[hidden email]> wrote:
>
>> On 2/14/06, Bert Freudenberg <[hidden email]> wrote:
>>> Also, I'd prefer directly publishing to a MC repository rather than
>>> uploading to Mantis.
>>>
>> Absolutely. I'd publish that sort of stuff in my own repository in
>> such a case and add pointers to Mantis.
>
> Er, so should I save the in-image package MCZs to the inbox
> repository? Or
> will whoever manages the inbox grab the MCZs from the Mantis bug
> report?
>
> frank
>
>
>