[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-core-devel
Subject: Re: KDE/4.11 branched what to do with kde-workspace?
From: Michael Jansen <info () michael-jansen ! biz>
Date: 2013-07-10 13:34:43
Message-ID: 59720065.Oa87Didr46 () gambit ! local ! michael-jansen ! biz
[Download RAW message or body]
On Wednesday, July 10, 2013 02:12:41 PM David Jarvie wrote:
> On Wed, July 10, 2013 1:19 pm, Martin Graesslin wrote:
> > On Wednesday 10 July 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 master will exists, but with a
> >> different content (and I assume unstable)?
> >
> > we have not yet talked about which branch we use. But just because we
> > switch to Qt 5 doesn't mean it will become unstable ;-)
> >
> >> Does it mean the KDE 4.11 branch of kde-workspace will be needed even
> >> for "master" users (or for KDE >4.11)?
> >
> > master is just a name one specifies in kdesrc-buildrc ;-) I don't think
> > that
> > this really matters to anyone except the developers of kde-workspace. And
> > if we do important changes I'm sure e.g. Aaron will blog about it.
>
> For those who don't use kdesrc-build, knowing which branch to use does
> matter. kdesrc-buildrc and blogging are fine, but there needs to be an
> simple way later on to know which branch to use, without having to search
> through config files which you don't have a copy of, or past blogs.
And there are people using my tool (build-tool). There are people using their own script and
some even doing it manually. There are the packagers who need to know. Not sure if there are
distros that track our development versions. Linux from scratch or so?
Because of that it should be announced. BIG TIME. I am not hopeful because this is the one
area we fail to get consistent all the time. Announcing our version control strategy, changes and
anything related. I know because i am subscribed to all relevant mailing lists and still fail to catch
many moves and changes. Only when stuff fails to compile i notice.
Mike
--
Michael Jansen
http://michael-jansen.biz
[Attachment #3 (unknown)]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" \
"http://www.w3.org/TR/REC-html40/strict.dtd"> <html><head><meta name="qrichtext" \
content="1" /><style type="text/css"> p, li { white-space: pre-wrap; }
</style></head><body style=" font-family:'Monospace'; font-size:10pt; \
font-weight:400; font-style:normal;"> <p style=" margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;">On Wednesday, July 10, 2013 02:12:41 PM David Jarvie wrote:</p> <p \
style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> On Wed, July 10, 2013 \
1:19 pm, Martin Graesslin wrote:</p> <p style=" margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;">> > On Wednesday 10 July 2013 01:25:06 Andras Mantia \
wrote:</p> <p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; \
margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> \
>> On Tuesday, July 09, 2013 11:45:39 PM Martin Graesslin wrote:</p> <p style=" \
margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> >> > * master \
is opened for feature development and will lead to Plasma</p> <p style=" \
margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> >> > Workspaces \
2 (or whatever the release will be called in the end).</p> <p style=" margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; \
text-indent:0px; -qt-user-state:0;">> >> </p> <p style=" margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; \
text-indent:0px; -qt-user-state:0;">> >> Does this mean that kde-workspace \
in master will exists, but with a</p> <p style=" margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;">> >> different content (and I assume unstable)?</p> <p \
style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > </p> <p style=" \
margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > we have not yet \
talked about which branch we use. But just because we</p> <p style=" margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; \
text-indent:0px; -qt-user-state:0;">> > switch to Qt 5 doesn't mean it will \
become unstable ;-)</p> <p style=" margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;">> > </p> <p style=" margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;">> >> Does it mean the KDE 4.11 branch of kde-workspace \
will be needed even</p> <p style=" margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;">> >> for "master" users (or for KDE \
>4.11)?</p> <p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; \
margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > \
</p> <p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > master is just a \
name one specifies in kdesrc-buildrc ;-) I don't think</p> <p style=" margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; \
text-indent:0px; -qt-user-state:0;">> > that</p> <p style=" margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; \
text-indent:0px; -qt-user-state:0;">> > this really matters to anyone except \
the developers of kde-workspace. And</p> <p style=" margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; \
text-indent:0px; -qt-user-state:0;">> > if we do important changes I'm sure \
e.g. Aaron will blog about it.</p> <p style=" margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;">> </p> <p style=" margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;">> For those who don't use kdesrc-build, knowing which branch to \
use does</p> <p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; \
margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> \
matter. kdesrc-buildrc and blogging are fine, but there needs to be an</p> <p style=" \
margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> simple way later on to \
know which branch to use, without having to search</p> <p style=" margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; \
text-indent:0px; -qt-user-state:0;">> through config files which you don't have a \
copy of, or past blogs.</p> <p style="-qt-paragraph-type:empty; margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; \
text-indent:0px; "> </p> <p style=" margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;">And there are people using my tool (build-tool). There are people \
using their own script and some even doing it manually. There are the packagers who \
need to know. Not sure if there are distros that track our development versions. \
Linux from scratch or so?</p> <p style="-qt-paragraph-type:empty; margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; \
text-indent:0px; "> </p> <p style=" margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;">Because of that it should be announced. BIG TIME. I am not hopeful \
because this is the one area we fail to get consistent all the time. Announcing our \
version control strategy, changes and anything related. I know because i am \
subscribed to all relevant mailing lists and still fail to catch many moves and \
changes. Only when stuff fails to compile i notice.</p> <p \
style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; \
margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> <p style=" \
margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Mike</p> <p \
style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; \
margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> <p style=" \
margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">-- </p> <p style=" \
margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Michael Jansen</p> <p style=" \
margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;">http://michael-jansen.biz</p></body></html>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic