Smalltalk › Pharo › Pharo Smalltalk Developers

Fwd: to go beta?

‹ Previous Topic Next Topic ›
 
classic Classic list List threaded Threaded
♦
♦
 5 messages Options
Stéphane Ducasse
Reply | Threaded
Open this post in threaded view
♦
♦
|

Fwd: to go beta?

Stéphane Ducasse
>
> Marcus, Adrian, Mike
> how do we proceed to go beta?
> take the 1.0 fixes and integrate them.
> put a deadline and do it?
>
> Stef
>
>
>


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Adrian Lienhard
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Fwd: to go beta?

Adrian Lienhard
That's a good question I was also thinking about today...

I suggest the following steps:

1. Review all issues in the tracker and decide for each whether it is  
important for 1.0.
2. We concentrate on completing these 1.0-tagged items. New issues  
should only be tagged with 1.0 if they are critical bugs (i.e., no new  
improvements get integrated anymore!)
3. As soon as we have completed all items that change the behavior of  
the system (i.e., that are not bugfixes) we declare beta
4. As soon as all items are done, we declare gamma and after a while  
without newly reported problems we release 1.0

Adrian

On Jun 11, 2009, at 21:59 , Stéphane Ducasse wrote:

>>
>> Marcus, Adrian, Mike
>> how do we proceed to go beta?
>> take the 1.0 fixes and integrate them.
>> put a deadline and do it?
>>
>> Stef
>>
>>
>>
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
gcotelli
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Fwd: to go beta?

gcotelli
I will try to rewrite this week the last dirty method (according to my count)... so the 1.0 should be license clean... . After this maybe I could help with some bugs.

On Thu, Jun 11, 2009 at 5:19 PM, Adrian Lienhard <[hidden email]> wrote:
That's a good question I was also thinking about today...

I suggest the following steps:

1. Review all issues in the tracker and decide for each whether it is
important for 1.0.
2. We concentrate on completing these 1.0-tagged items. New issues
should only be tagged with 1.0 if they are critical bugs (i.e., no new
improvements get integrated anymore!)
3. As soon as we have completed all items that change the behavior of
the system (i.e., that are not bugfixes) we declare beta
4. As soon as all items are done, we declare gamma and after a while
without newly reported problems we release 1.0

Adrian

On Jun 11, 2009, at 21:59 , Stéphane Ducasse wrote:

>>
>> Marcus, Adrian, Mike
>>      how do we proceed to go beta?
>>      take the 1.0 fixes and integrate them.
>>      put a deadline and do it?
>>
>> Stef
>>
>>
>>
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
SergeStinckwich
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Fwd: to go beta?

SergeStinckwich
In reply to this post by Adrian Lienhard
On Fri, Jun 12, 2009 at 3:19 AM, Adrian Lienhard<[hidden email]> wrote:

> That's a good question I was also thinking about today...
>
> I suggest the following steps:
>
> 1. Review all issues in the tracker and decide for each whether it is
> important for 1.0.
> 2. We concentrate on completing these 1.0-tagged items. New issues
> should only be tagged with 1.0 if they are critical bugs (i.e., no new
> improvements get integrated anymore!)
> 3. As soon as we have completed all items that change the behavior of
> the system (i.e., that are not bugfixes) we declare beta
> 4. As soon as all items are done, we declare gamma and after a while
> without newly reported problems we release 1.0


What could be great is a release during next ESUG conference in september.

--
Serge Stinckwich
UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam
Smalltalkers do: [:it | All with: Class, (And love: it)]
http://doesnotunderstand.org/

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Marcus Denker-3
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Fwd: to go beta?

Marcus Denker-3
In reply to this post by Adrian Lienhard

On 11.06.2009, at 16:19, Adrian Lienhard wrote:

> That's a good question I was also thinking about today...
>
> I suggest the following steps:
>
> 1. Review all issues in the tracker and decide for each whether it is
> important for 1.0.
> 2. We concentrate on completing these 1.0-tagged items. New issues
> should only be tagged with 1.0 if they are critical bugs (i.e., no new
> improvements get integrated anymore!)
> 3. As soon as we have completed all items that change the behavior of
> the system (i.e., that are not bugfixes) we declare beta
> 4. As soon as all items are done, we declare gamma and after a while
> without newly reported problems we release 1.0

Yes, that makes sense.

I did a pass over the last days to close / harvest the most simple small
changes (e.g. small cleanups). We are down to 257 open bug reports.


        Marcus

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Free forum by Nabble Edit this page