[Kde-games-devel] porting and the next release of knights

[Alexander Semke]

Am Mittwoch, 6. Januar 2016, 23:28:48 schrieben Sie:
> > Ok. I'd like to do the following as next:
> > 1. push Manoharan's diff to master and cherry-pick two or three relevant
> > commits from frameworks to master
> 
> He can do that too
I asked him on Sunday whether he can already push to remote or not. There was 
no answer yet and I proposed my help here.


> > 4. For further development a new developmet branch will be created after
> > the next release.
> 
> Why would you create a new branch? Just use master like everyone else does,
> no?
Yes, master will be used for doing releases and the new development branch for 
doing new development. What I wanted to say was that we can develop, fix and 
port everything now in master until everything is ready for the next release. 
There is no need to introduce new branches at this stage since we won't 
release from master until everything is done. Once the next release is done, 
new development branch(es) will be created for further development that get 
then later merged to master for further releases. I think this is also what 
you meant in one of your previous emails with "What we do in applications that 
are part of the KDE Applications bundle (knights is not) is basically you have 
one stable relesae and one development branch".


-- 
Alexander