Am 16.06.2012, 06:25 Uhr, schrieb Scott Kitterman k...@kitterman.com:
On Friday, June 15, 2012 01:05:44 PM Sebastian Kügler wrote:
As an example, Frameworks could release updates every 2 months, while
our
application collection is updated monthly. New iterations of the
workspaces
come
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/105222/#review14775
---
Ping?
- Xuetian Weng
On June 12, 2012, 1:37 a.m., Xuetian
i like where this is going..i've always wanted a bit more flexibility
in releases...
one thing to keep in mind (i realize it's a bit premature to say this,
but..) we'd definitely have to make sure we coordinate the various
freezes well, since there'd be a dedicated and specialized
freeze-timeline
This proposal looks like the X.org release cycle.
Each individual component can release as many versions as wanted, and
from time to time there will be a global release.
2012/6/16 Shaun Reich sre...@kde.org:
i like where this is going..i've always wanted a bit more flexibility
in releases...
On Saturday 16 June 2012, Shaun Reich wrote:
and the freezes would have to be *very* well communicated, because
even now we run into issues with people not realizing that we're in
string freeze or feature freeze.
a part of the plan (kindof a consequency in the long term of the thing
Ahoy,
On Fri, Jun 15, 2012 at 1:05 PM, Sebastian Kügler seba...@gmail.com wrote:
Starting with KDE Frameworks 5, we will release Frameworks, Workspaces and
Applications each with their own release cycles. Each of these releases would
be a set of tarballs of the latest stable versions of the
On Sat, Jun 16, 2012 at 1:21 PM, Marco Martin notm...@gmail.com wrote:
On Saturday 16 June 2012, Shaun Reich wrote:
and the freezes would have to be *very* well communicated, because
even now we run into issues with people not realizing that we're in
string freeze or feature freeze.
a part
On June 15, 2012, 11:38 p.m., Steven Sroka wrote:
Martin, what's the status of this patch? I think a bunch of bug reports on
bko are waiting to get closed ;)
There was a mail thread on core-devel for this and Thiago Macieira said it's
the wrong approach.
I'll remove the patch ...
-
Starting with KDE Frameworks 5, we will release Frameworks, Workspaces and
Applications each with their own release cycles. Each of these releases
would
be a set of tarballs of the latest stable versions of the application (or
codebase in more general).
As an example, Frameworks could
On May 27, 2012, 1:53 p.m., Vishesh Handa wrote:
nepomuk/kcm/statuswidget.cpp, line 185
http://git.reviewboard.kde.org/r/102523/diff/2/?file=65254#file65254line185
Commit these icon changes in a separate patch. (No need to open a
review request)
ping? Any updates on this?
-
On Sat, Jun 16, 2012 at 7:21 AM, Marco Martin notm...@gmail.com wrote:
a part of the plan (kindof a consequency in the long term of the thing
described here) is that it would mean aiming to a state where there are nover
freezes (or well, master is always frozen, depends how you look at ;)
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/105278/#review14799
---
kdeui/actions/kaction.cpp
On Friday, June 15, 2012 13:05:44 Sebastian Kügler wrote:
Hi all,
During our sprint in Pineda de Mar, we sat down and thought about how our
release cycles relate to the structures in our software, we came up with
the following proposal we'd like you to consider and provide feedback
about.
13 matches
Mail list logo
