Updating Mantis status

Edgar J. De Cleene edgardec2001 at yahoo.com.ar
Fri Feb 8 12:41:27 UTC 2008




El 2/8/08 7:11 AM, "Ben Goetter" <goetter at mazama.net> escribió:

> 
> Seconded with a newbie's enthusiasm.
> 
> I'm more than a little confused about the Mantis workflow.  As an
> example(*), consider http://bugs.squeak.org/view.php?id=3311, where an
> individual identifies some lossage in the existing Complex class, then
> proposes a replacement class addressing the identified problems.
> 
> In every project that I've known before, this would have been accepted
> into some build, or else deferred, or else rejected outright.  (By whom?
>   By some cabal or benevolent dictator.  All those projects have had
> such.)  Instead, this fix has simply sat there, apparently without
> comment, for the last two years.
> 
> So I don't really see how Mantis works(**).  Yes, there's a place to
> report problems.  But do fixes come out of it?  If as part of a project
> of mine I can address some open issues therein, will they ever reach the
> mainstream?  May I just step in and claim a bug on my own, filing a
> suggested fix for it?  Also, if as part of a project of mine I can
> factor out some baseline kernel improvements, should I bother proposing
> them in Mantis?  Or should I just dump those base-class amendments into
> my package and let client handle the merge themselves?  A lot of the
> latter takes place right now....
> 
> I'm not asking that anything change to accommodate my expectations.  I
> just want to understand how to work here.
> 
> Cheers,
> Ben


I remember the requeriments Ralph put for 3.10 (that's why less updates as
older Squeak releases)

>In general, changes will come through Mantis (the squeak bugs and changes
>management system). Ideally, a Mantis patch will be a [[Monticello]] package,
but we will also accept .cs files, though we will first convert them to .mcz
Monticello files. Ideally, changes will be approved by one of the stewards,
though if code does not have a steward or if the stewards are not responsive,
the release team will approve them.

All should come with test, and with other Squeaker saying this is a good
change.
Then
>   1. Loading bug tests before fixes.
>   2. Run the bug test. (It should fail)
>   3. Install the fix.
>   4. Run the bug test. (Now it should pass.)

All this and the most of 2000 Sunit test which I run on Mac, Windows XP and
Linux don't guarantee Squeak is Bug free.
We have cases on some bugs with long reports, cases of Monticello headaches
and my own mistakes.
But I put some old Mantis report on 3.10...

3.10 end, I wish start 3.11 and must wait some agree on my proposal or do
some better proposal.

Edgar








More information about the Squeak-dev mailing list