On 11/03/2010 12:39 AM, Pavel Sanda wrote:
Vincent van Ravesteijn wrote:
I wanted to propose to start the 2.0.x branch when you enter the
feature-freeze/beta state. This would allow to continue redesigning and
refactoring the code, because I stumble on this everytime I try to fix real
problems in the codebase.
we can discuss it. what i fear is that people stop focus on 2.0 and start to
work
new games in trunk.
As always, people will always do what they want. It's the job of the
maintainer to recall the relevent developer his duty with regards to the
branch bug fixing. And Juergen is very goo at it. Artificially imposing
a limit on trunk because we don't want developpers to lose their focus
is not needed IMO.
that said i'm aware that exactly you dont fit into this category
and your 1.6 bugfixing activity during 2.0 development was just perfect.
it will most probably also reduce our testing for 2.0, since most people
will just continue trunk...
People should have two checkout: branch and trunk, period.
another possibility is that you create personal branch is push the changes
there.
people will still see changelongs and can comment on them.
Above 2 branches, svn branching is a nightmare so no. Personal branch is
not a solution.
lets hear what other people think.
I would like to propose that we migrate new development to git. And that
current svn trunk stays the 2.0.x development platform. In git I would
impose that each new feature is done in a new git branch.
I would also like to propose that we switch to a fixed date release cycle:
- feature release every six months.
- lyx format changing release every two years (or less)
Abdel.
