Michal Čihař a écrit :

Hi

Dne Wed, 01 Dec 2010 06:14:47 -0500 Marc Delisle marc@infomarc.info napsal(a):

...

I realize that I started QA_3_4 too soon. It only needs to begin when 3.4.0 (final) is released. I'll remove it.

...

From now on we should focus on stabilizing MAINT_3_4_0; new features

would go to master only.

If it makes sense to fix a bug in QA_3_3 (for 3.3.9) we do it; then we merge to MAINT_3_4_0 and master.

Do we really need MAINT_3_4_0 at this point?

Only if someone plans to add new features to master. But indeed if we are really disciplined we don't need it.

2010/12/1 Marc Delisle marc@infomarc.info:

Marc Delisle a écrit :

...

Michal Čihař a écrit :

...

Hi

Dne Wed, 01 Dec 2010 06:14:47 -0500 Marc Delisle marc@infomarc.info napsal(a):

...

I realize that I started QA_3_4 too soon. It only needs to begin when 3.4.0 (final) is released. I'll remove it.

...

From now on we should focus on stabilizing MAINT_3_4_0; new features

would go to master only.

If it makes sense to fix a bug in QA_3_3 (for 3.3.9) we do it; then we merge to MAINT_3_4_0 and master.

Do we really need MAINT_3_4_0 at this point?

Only if someone plans to add new features to master. But indeed if we are really disciplined we don't need it.

Does someone plan to add features to master before 3.4.0 is out? We are talking about a few months.

Hi all,

Probably not, I will do mainly bug fixing.

Snowy greetings,

Dieter

On 02-12-10 09:14, Michal Čihař wrote:

Hi

Dne Wed, 01 Dec 2010 11:42:26 -0500 Marc Delisle marc@infomarc.info napsal(a):

...

Does someone plan to add features to master before 3.4.0 is out? We are talking about a few months.

I think we should focus on bug fixing right now. It might make sense to split out QA_3_4 around rc phase, when not that much changes should happen.

I fully agree, these extra branches mainly consume precious time. And in-case someone want to work on some experimental feature we can always make a feature branch.