Marc Delisle schrieb:

Sebastian Mendel a écrit :

...

Marc Delisle schrieb:

...

Hi,

I think we could freeze the messages for 2.9.0 and prepare for 2.9.0-beta1.

Also, I might release 2.8.2.1 tomorrow (not from QA_2_8) with backports

not from QA_2_8 ?

why not?

I should check again what's in QA_2_8 but this branch is supposed to be for 2.8.3.

yes, i missread it a little bit

However I just wanted to release some quick fixes that would be against MAINT_2_8_2 (I have to create this branch). And I think that it's not necessary to call this 2.8.3.

yes, this was in my mind too

Do you prefer a 2.8.2.1 from QA_2_8 ?

no, i would prefer a branch QA?|MAINT?_2_8_2 from the point where 2.8.2 was released, and backport the suggested fix into there and release 2.8.2.1 from there

... but it is your work ... ;-)

Michal Čihař a écrit :

Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:

...

Also, I might release 2.8.2.1 tomorrow (not from QA_2_8) with backports of these fixes:

• detect new config.inc.php (need to close all browser windows)
• IE6 on IIS blank frame (trivial fix but will be appreciated by users)

Anything else urgent to backport?

There is already ported setup.php in QA which fixes issues with escaping strings written to config and compatibility with old php. I think it should be in release.

Sebastian Mendel a écrit :

...

Do you prefer a 2.8.2.1 from QA_2_8 ?

no, i would prefer a branch QA?|MAINT?_2_8_2 from the point where 2.8.2 was released, and backport the suggested fix into there and release 2.8.2.1 from there

Ok, Michal's fix is the only one included in QA_2_8. Normally QA_2_8 should be for 2.8.3 but we'll make an exception since the difference between 2.8.2 and 2.8.2 will be so light.

So I'll backport some fixes to QA_2_8 and release 2.8.2.1 from it.

Marc