I submitted a change set to squeak-dev using a menu choice in the changes
browser. Is this the best way to submit changes for consideration? How are things evaluated, tested, incorporated into squeak? I looked at the Morphic mailing list and it seems to be effectively inactive - could the purpose of that list be made more general (at the moment it supposed to be for managers of Morphic but the discussion is all about people not doing anything about it). The changes that I am suggesting make Morphic more readily drivable from direct coding - I'd welcome any feedback from those who see the point of this. The change set is in MorphicMessageFix in squeak-dev. Bob |
Incorporating changes
Hi Robert, The best place for this info would be to start a Mantis report. (You can get a mantis acct freely and easily). A good place to start is: http://bugs.impara.de/my_view_page.php Mantis provides a patient persistent way to focus on an issue. I use it to accumulate data on a problem until a solution can be found. It provides a place to alert the community to a problem; -accumulate facts and clues from the analysis; -publish preposed solutions and get feedback; -get solutions havested and included into the main stream. >Robert Hawley rhawley at plymouth.ac.uk >Thu Oct 5 23:50:43 UTC 2006 wrote: >I submitted a change set to squeak-dev using a menu choice in the changes >browser. Is this the best way to submit changes for consideration? How are >things evaluated, tested, incorporated into squeak? This is a good question and usually a new answer needs to be invented each time it's asked. You will have to get a definitive answer from the people who do the havesting and the releasing. >From the poin of view of someone who enjoys making fixes. I just do them and post them on mantis and then wait patiently until they get noticed. Work effort is decentralized an potluck. If you care about something you have to present it in an intriging enough way that you attract allies. > >I looked at the Morphic mailing list and it seems to be effectively inactive I am still waiting for a reply to my last post. http://lists.squeakfoundation.org/pipermail/morphic/2006-July/000151.html Morphic is in a bit of a pickle right now. The fellow who was heading the team stepped down when he realized the work he had let himself in for wasn't what he imagined it would be when he took the job. No one has stepped in yet to take over his role. I have a great fondness for morphic and I dabble in morphic fixes and enhancements. I've been toying with the idea of reviving the list and repurposing it to talk about morphic fixes and maintenence. Until there are a core of (communicating) people with a common enough interest in Morphic maintenence that toy remains dormant. >- could the purpose of that list be made more general (at the moment it >supposed to be for managers of Morphic but the discussion is all about >people not doing anything about it). The action you seek (focused discussions on actual fixes) is on Mantis. > >The changes that I am suggesting make Morphic more readily drivable from >direct coding - I'd welcome any feedback from those who see the point of >this. The change set is in MorphicMessageFix in squeak-dev. > >Bob Yours in service, -- Jerome Peace __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
Peace Jerome puso en su mail :
> Morphic is in a bit of a pickle right now. The fellow > who was heading the team stepped down when he realized > the work he had let himself in for wasn't what he > imagined it would be when he took the job. No one has > stepped in yet to take over his role. Very unfair, as Juan do a great job > > I have a great fondness for morphic and I dabble in > morphic fixes and enhancements. > > I've been toying with the idea of reviving the list > and repurposing it to talk about morphic fixes and > maintenence. Until there are a core of (communicating) > people with a common enough interest in Morphic > maintenence that toy remains dormant. You know me, I was on the first team and on the second. And you know could work together. Maybe it's time to start to do something ? What this time could be needed no people without some hours exploring MorphicLand in team. And what decisions made by the team was listened. Without that, I have enough Squeak for playing myself. Edgar __________________________________________________ Preguntá. Respondé. Descubrí. Todo lo que querías saber, y lo que ni imaginabas, está en Yahoo! Respuestas (Beta). ¡Probalo ya! http://www.yahoo.com.ar/respuestas |
In reply to this post by rhawley
Hi robert
In this moment we are in release phase so only little crucial fixes are incorporated. The best way to increase the chances of a bug fixes is - make clear why this is important - document - document with tests if possible Stef On 6 oct. 06, at 01:50, Robert Hawley wrote: > I submitted a change set to squeak-dev using a menu choice in the > changes > browser. Is this the best way to submit changes for consideration? > How are > things evaluated, tested, incorporated into squeak? > > I looked at the Morphic mailing list and it seems to be effectively > inactive > - could the purpose of that list be made more general (at the > moment it > supposed to be for managers of Morphic but the discussion is all about > people not doing anything about it). > > The changes that I am suggesting make Morphic more readily drivable > from > direct coding - I'd welcome any feedback from those who see the > point of > this. The change set is in MorphicMessageFix in squeak-dev. > > Bob > > |
Free forum by Nabble | Edit this page |