El Diumenge, 17 d'agost de 2014, a les 21:47:09, Christoph Feck va escriure: > On Wednesday 04 June 2014 23:00:26 Albert Astals Cid wrote: > > Ok, so basically do: > > * 4.14 as planned > > * 4.15 but we don't call it 4.15 and we call it 14.12 and contains > > > > kdelibs4/qt4 and kf5 based applications > > How do we manage which branches are used for the next application > releases? > > Let's say we have an application KMyApp, where the aim is to not > further improve the kdelibs4 version, but port to KF5. > > Will that application be released from a new "KDE/14.12" branch, or > from the old "KDE/4.14" branch? > > The actual question is: Are we save to merge "frameworks" to "master", > without risking that unfinished work is branched for release later? Or > do we need to keep "master" always stable, and only merge "frameworks" > when it is ready for release?
Personally i think the development model should not change, that is, master is the branch we're going to release next, so if you merge frameworks to it, make sure it'll be ready for December. Cheers, Albert P.S: Yes we can make exceptions if shit happens and stuff doesn't get done on time, but please note that each exception makes release engineering harder, so if you make your master KF5 based, i'd expect a commitment of 99% to have it good and running for the next release. > > Christoph Feck (kdepepo) > > >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe > >> << >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
