Hi Koen,

You’re right. It is on the radar for the release. I just added the tag.
There is no formal process to identify them but if one feel a bug is really 
annoying and should be fixed before the release, he/she can inform us on the 
list.

Cheers,
Christophe

> Le 22 févr. 2024 à 15:46, Koen De Hondt <[email protected]> a 
> écrit :
> 
> Esteban,
> 
> I see that some issues are tagged with To fix before release 
> <https://github.com/pharo-project/pharo/issues?q=is%3Aissue+is%3Aopen+label%3A%22To+fix+before+release%22>
> 
> What is the process to decide what to fix before the release?
> 
> Can we add issues? In particular, this issue is very annoying:
> 
> 
> https://github.com/pharo-project/pharo/issues/15564
> 
> 
> I do not see the same tags in https://github.com/pharo-spec/Spec. Does that 
> mean that no Spec issues are selected to be fixed before the release?
> 
> Ciao,
> Koen
> 
> 
>> On 13 Feb 2024, at 11:25, Esteban Lorenzano via Pharo-dev 
>> <[email protected]> wrote:
>> 
>> Hi,
>> 
>> The development of Pharo 12 will enter in feature freeze on March 1st and we 
>> plan to have at least one month of stabilization (but we will release when 
>> we are ready, in April).
>> 
>> cheers,
>> 
>> Esteban
>> 
>> 
> 

Reply via email to