---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/111480/
---
Review request for kde-workspace.
Description
---
Do not replace
Le mercredi 10 juillet 2013 17:55:42 Àlex Fiestas a écrit :
On Tuesday 09 July 2013 16:12:35 Andras Mantia wrote:
Two point I want to mention:
1) working in a branch for kdepim is quite painful, as you need actually
work on branches of 3 (or sometimes 4) modules: kdepimlibs,
On Wednesday, July 10, 2013 01:25:06 Andras Mantia wrote:
On Tuesday, July 09, 2013 11:45:39 PM Martin Graesslin wrote:
* master is opened for feature development and will lead to Plasma
Workspaces 2 (or whatever the release will be called in the end).
Does this mean that kde-workspace in
Hi,
On Tuesday, July 09, 2013 23:45:39 Martin Graesslin wrote:
On Tuesday 09 July 2013 18:57:41 Albert Astals Cid wrote:
So the kde-workspace dudes decided they don't want a 4.12 release and that
they'll do a LTS 4.11, fine, how do we fix that branch wise?
I don't see how that affects
Hi,
2013/7/11 Sebastian Kügler:
Hi,
On Tuesday, July 09, 2013 23:45:39 Martin Graesslin wrote:
On Tuesday 09 July 2013 18:57:41 Albert Astals Cid wrote:
So the kde-workspace dudes decided they don't want a 4.12 release and that
they'll do a LTS 4.11, fine, how do we fix that branch wise?
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/111480/
---
(Updated July 11, 2013, 1:54 p.m.)
Review request for kde-workspace and
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/111480/#review35860
---
This has the side-effect that the Copy finished message when
What about a single official development branch?
Just use two branches:
- master branch (stable)
- kdevel branch (devel)
You develop wherever you like and push things on kdevel branch when
ready. If you like the one branch approach, you devel things directly in
kdevel branch.
People knows there
Àlex Fiestas afies...@kde.org wrote:
On Wednesday 10 July 2013 13:22:20 Sune Vuorela wrote:
On 2013-07-09, Sune Vuorela nos...@vuorela.dk wrote:
So. first one.
Second one
Release frequency.
We have a giant quality problem. Distros won't ship a .0 release to
real
users (as opposed to
On Thursday 11 July 2013, andrea diamantini wrote:
What about a single official development branch?
Just use two branches:
- master branch (stable)
- kdevel branch (devel)
You develop wherever you like and push things on kdevel branch when
ready. If you like the one branch approach, you
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/111335/
---
(Updated July 11, 2013, 11:37 p.m.)
Review request for kdelibs.
Changes
11 matches
Mail list logo
