Smalltalk › Squeak › Squeak - Dev

Towards a Trunk Release [help needed]

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

28 messages Options

Bert Freudenberg

Re: Towards a Trunk Release [help needed]

On 20.02.2010, at 23:58, Chris Muller wrote:

>
>> This is part two of two about upcoming releases. Besides the 4.0 release we
>> need to get ready for a release from the trunk. If you look at rather long
>> list of improvements this is a good time to get a release out.
>
> Yes, but there are still some basic things we should try to fix
> shouldn't we? For example, it's hard to imagine putting out something
> called anything other than "alpha" with the TextEditor home / end keys
> are not working properly. Things like this are too low-level to allow
> into a final release because people have a connection to software
> through their mouse, keyboard, and have expectations for certain keys
> to behave in the normal ways.
>
> If it were the backspace key, I'm sure we wouldn't release. To me the
> home and end keys are right up there..

One of the jobs of the release manager would be to determine which of the bugs are blockers for the release. They could be tagged on Mantis, maybe create a report showing all of them, and then we can work steadily towards fixing those issues.

- Bert -

Edgar J. De Cleene

Re: Towards a Trunk Release [help needed]

On 2/21/10 9:21 AM, "Bert Freudenberg" <[hidden email]> wrote:

> One of the jobs of the release manager would be to determine which of the bugs
> are blockers for the release. They could be tagged on Mantis, maybe create a
> report showing all of them, and then we can work steadily towards fixing those
> issues.
>
> - Bert -

The release manager send friendly responses to two super Squeakers saying
they wish help.

Also to two who do not say , but I need they could help.

Silence...

And the release manager beg Board say

"Well the 9371 is the last 3.11 until further notice, you could consider it
the end of this phase, no more new things, no more changes until you happy
all works and user do not go away after the n + 1 crash "

I send a proposal about Mendieta.

Having some coming from my wild experiments working, say some yesterday in
IRC.

Feedback, please feedback.

On Skype and on IRC as edgardec until 12:30 Argentina (two more hours)

Edgar

garduino

Re: Towards a Trunk Release [help needed]

Hi Edgar!

2010/2/21 Edgar J. De Cleene <[hidden email]>

On 2/21/10 9:21 AM, "Bert Freudenberg" <[hidden email]> wrote:

> One of the jobs of the release manager would be to determine which of the bugs
> are blockers for the release. They could be tagged on Mantis, maybe create a
> report showing all of them, and then we can work steadily towards fixing those
> issues.
>
> - Bert -

The release manager send friendly responses to two super Squeakers saying
they wish help.

Also to two who do not say , but I need they could help.

Silence...

And the release manager beg Board say

"Well the 9371 is the last 3.11 until further notice, you could consider it
the end of this phase, no more new things, no more changes until you happy
all works and user do not go away after the n + 1 crash "

I send a proposal about Mendieta.

Having some coming from my wild experiments working, say some yesterday in
IRC.

Feedback, please feedback.

On Skype and on IRC as edgardec until 12:30 Argentina (two more hours)

Edgar

I also think that the current 3.11 (or the new name it will have) should be freezed at some point,
without new additions.

But, and sorry if I'm so repetitive, can't understand how Shout is being used on it.

The class browser show the highlighted syntax, but if you check on Universes
(in Category "Code Browsing") the main Shout package is not installed.

I would understand how is implemented Shout in 3.11, because if you install the
Shout Workspace not works and neither the Shout-Monticello.

Cheers.
Germán.

Andreas.Raab

Re: Towards a Trunk Release [help needed]

In reply to this post by Chris Muller-3

Chris Muller wrote:
>> This is part two of two about upcoming releases. Besides the 4.0 release we
>> need to get ready for a release from the trunk. If you look at rather long
>> list of improvements this is a good time to get a release out.
>
> Yes, but there are still some basic things we should try to fix
> shouldn't we?

Absolutely. As usual, the point of getting into "release mode" is that
you stop just adding more stuff which potentially destabilize things and
rather try to polish the release by fixing all the little nit-picks that
have gone unfixed thus far.

BTW, the best way to ensure the things you care about do get fixed is to
file a bug with a test. The bug ensures the issue doesn't get forgotten
for the release, the test ensures no regressions.

Cheers,
- Andreas

> For example, it's hard to imagine putting out something
> called anything other than "alpha" with the TextEditor home / end keys
> are not working properly. Things like this are too low-level to allow
> into a final release because people have a connection to software
> through their mouse, keyboard, and have expectations for certain keys
> to behave in the normal ways.
>
> If it were the backspace key, I'm sure we wouldn't release. To me the
> home and end keys are right up there..
>
>

Casey Ransberger

Re: Towards a Trunk Release [help needed]

Hooray for tests!

On Mon, Feb 22, 2010 at 3:30 AM, Andreas Raab <[hidden email]> wrote:

> Chris Muller wrote:
>>>
>>> This is part two of two about upcoming releases. Besides the 4.0 release
>>> we
>>> need to get ready for a release from the trunk. If you look at rather
>>> long
>>> list of improvements this is a good time to get a release out.
>>
>> Yes, but there are still some basic things we should try to fix
>> shouldn't we?
>
> Absolutely. As usual, the point of getting into "release mode" is that you
> stop just adding more stuff which potentially destabilize things and rather
> try to polish the release by fixing all the little nit-picks that have gone
> unfixed thus far.
>
> BTW, the best way to ensure the things you care about do get fixed is to
> file a bug with a test. The bug ensures the issue doesn't get forgotten for
> the release, the test ensures no regressions.
>
> Cheers,
> - Andreas
>
>> For example, it's hard to imagine putting out something
>> called anything other than "alpha" with the TextEditor home / end keys
>> are not working properly. Things like this are too low-level to allow
>> into a final release because people have a connection to software
>> through their mouse, keyboard, and have expectations for certain keys
>> to behave in the normal ways.
>>
>> If it were the backspace key, I'm sure we wouldn't release. To me the
>> home and end keys are right up there..
>>
>>
>
>
>

--
Ron

Gary Dunn

Re: Towards a Trunk Release [help needed]

On Wed, 2010-03-03 at 21:26 -0800, Ronald Spengler wrote:
> Hooray for tests!

I ran some tests on the Squeak3.11-9371-alpha.image and posted the
results to

http://wiki.squeak.org/squeak/6148

Others have listed what failed. How do I generate that listing?

--
Gary Dunn, Honolulu
[hidden email]
http://openslate.net/
http://e9erust.blogspot.com/
Sent from Slate001

Edgar J. De Cleene

Re: Towards a Trunk Release [help needed]

On 3/4/10 5:09 AM, "Gary Dunn" <[hidden email]> wrote:

> I ran some tests on the Squeak3.11-9371-alpha.image and posted the
> results to
>
> http://wiki.squeak.org/squeak/6148
>
> Others have listed what failed. How do I generate that listing?

Until now by using halos, you click on the panel until you select some like
a PluggableListMorphPlus<Failure List>(306) .

Inspect with the wrench item , look for #list or do self list inspect in the
lower pane of inspector.

I think a good exercise is figure how you could have this exported as a file
in your working dir.

Hints: the model of the window is TestRunner, look and you quick find
failedList ....

Keep the good work , its a valuable info discover the 64bit experimental Vm
gives 10 failures and the regular one 15.

Edgar

Bert Freudenberg

Re: Towards a Trunk Release [help needed]

On 04.03.2010, at 09:10, Edgar J. De Cleene wrote:

>
>
>
>
> On 3/4/10 5:09 AM, "Gary Dunn" <[hidden email]> wrote:
>
>> I ran some tests on the Squeak3.11-9371-alpha.image and posted the
>> results to
>>
>> http://wiki.squeak.org/squeak/6148
>>
>> Others have listed what failed. How do I generate that listing?
>
> Until now by using halos, you click on the panel until you select some like
> a PluggableListMorphPlus<Failure List>(306) .
>
> Inspect with the wrench item , look for #list or do self list inspect in the
> lower pane of inspector.

Or simply choose "copy & print... - copy text" from the halo's red menu button.

- Bert -