IMPORTANT: Pharo 12 will enter feature freeze on March 1st

EL
Esteban Lorenzano
Tue, Feb 13, 2024 10:25 AM

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

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
GP
Guillermo Polito
Tue, Feb 13, 2024 11:00 AM

Thanks Esteban.

Everybody, please join us in the bugfixing phase to have a robust release!

G

El 13 feb 2024, a las 11:25, Esteban Lorenzano via Pharo-dev pharo-dev@lists.pharo.org escribió:

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

Thanks Esteban. Everybody, please join us in the bugfixing phase to have a robust release! G > El 13 feb 2024, a las 11:25, Esteban Lorenzano via Pharo-dev <pharo-dev@lists.pharo.org> escribió: > > 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 > >
KD
Koen De Hondt
Thu, Feb 22, 2024 2:46 PM

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
No menubar in Mac OS Sonoma · Issue #15564 · pharo-project/pharo
github.com

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 pharo-dev@lists.pharo.org 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

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 No menubar in Mac OS Sonoma · Issue #15564 · pharo-project/pharo github.com 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 <pharo-dev@lists.pharo.org> 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 > >
CD
Christophe Demarey
Thu, Feb 22, 2024 2:58 PM

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 koen@all-objects-all-the-time.st 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 pharo-dev@lists.pharo.org 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

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 <koen@all-objects-all-the-time.st> 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 <pharo-dev@lists.pharo.org> 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 >> >> >