[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-panel-devel
Subject:    Re: [Panel-devel] RFC: release management strategy
From:       "Jos Poortvliet" <jos () mijnkamer ! nl>
Date:       2007-08-30 10:28:29
Message-ID: 5c77e14b0708300328h1c1dc485i8a79d268516f8d9a () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

[Attachment #4 (text/plain)]

On 8/30/07, Kevin Ottens <ervin@kde.org> wrote:
>
> Le mercredi 29 août 2007, Aaron J. Seigo a écrit :
> > i've never really liked kdeaddons, either. so here's my proposal:
> >
> > - we keep the set of items in kdebase/workspace/plasma *minimal*. these
> > should be core functionality items only. i'd like to have an irc meeting
> in
> > 2 weeks time to settle on which those will be.
>
> Sounds fair, you know that I'd like to see kdebase minimal anyway,
> providing
> the basic desktop features, so I'm clearly biased here.
>
> > - we create extragear/plasma/ with subdirs for dataengines/, runners/,
> > applets/, plasmoids/, scriptengines/ and possibly animators/ (if any new
> > ones appear =). people move their own work as they want into
> > extragear/plasma/. plasmoids/ would house non-c++ packages. we will
> cover
> > which items to move over now at that irc meeting.
> >
> > - we create a place for sample applets; perhaps in extragear as well?
> e.g.
> > extragear/plasma/samples/ with all the subdirs under there? i don't want
> to
> > lose all the samples; i think they are valuable and should be
> maintained.
> > they shouldn't be installed, or shipped, by default but be there for
> > documentary and educational purposes.
>
> Maybe it's better to keep them along the plasma libraries then? As a
> developer
> I like to find the examples with the code of the library I'm about to use
> (phonon and solid follow this pattern).
>
> > - there will be *no* plasma stuff in kdeaddons. this could be seen as my
> > desire to kill kdeaddons outright, which would be accurate. ;)
> >
> > then releases will happen like this:
> >
> > - everything gets released with each KDE release, extragear included
>
> w00t!
>
> > - we do a source only snapshot release of plasma itself for our more
> > devoted testers one a month. this is assuming KDE itself doesn't get
> into
> > this game so we don't have to.
>
> Hmmm, reminds me something... :-p
>
> > but even if KDE as a whole doesn't do
> > periodic snapshots, i want to for plasma. maybe plasma could serve as a
> > test case here for the rest of KDE if need be
>
> Looks fair.
>
> > - we do a snapshot release of extragear every 2 weeks, hopefully as
> proper
> > releases including binaries for as many platforms as possible. we need
> to
> > look into availability of services such as OpenSUSE's build system as i
> > really don't want to set up and maintain a network of systems ourselves
> =)
>
> I'm not sure about the 2 weeks thing, at this rate (and because of our
> current
> organisation where we definitely don't branch enough) you'll end up
> snapshoting non building or broken stuff.
>
> Actually, the 1 month snapshot rate we discussed a while ago was my
> pessimistic view because of our current way of working. If we had a SCM
> that
> allows us to branch more (means cheap branching, fast switching, both way
> merges that don't kill the history) then push changes in the main when
> ready
> I'd push to two weeks even for KDE itself.
>
> > what this means is that we can get people trying out new addons all the
> > time and keep the GHNS2 constantly repo fresh. it also means that kde
> > releases are full of all the plasma goodies up to that point in time.
> > hooray.
>
> With regular snapshots like this you probably want to be able to separate
> the "stable build", from the "snapshot builds" when the user retrieves the
> stuff. Does GHNS2 provide this kind of information? (I'm really clueless
> regarding GHNS2 features)
>
> > proposed irc meeting day: saturday sept 8th. please rsvp =)
>
> Right, any time during the day? or you envision a 24h meeting? ;-)


What, something wrong with that? Where are your hardcore feelings?


(sorry, but I couldn't resist. Usually, this is Wade's job, I know... Sorry
to step on your toes, W!)

Regards.
>

[Attachment #5 (text/html)]

On 8/30/07, <b class="gmail_sendername">Kevin Ottens</b> &lt;<a \
href="mailto:ervin@kde.org">ervin@kde.org</a>&gt; wrote:<div><span \
class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px \
solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Le mercredi \
29 août 2007, Aaron J. Seigo a écrit :<br>&gt; i&#39;ve never really liked \
kdeaddons, either. so here&#39;s my proposal:<br>&gt;<br>&gt; - we keep the set of \
items in kdebase/workspace/plasma *minimal*. these<br> &gt; should be core \
functionality items only. i&#39;d like to have an irc meeting in<br>&gt; 2 weeks time \
to settle on which those will be.<br><br>Sounds fair, you know that I&#39;d like to \
see kdebase minimal anyway, providing <br>the basic desktop features, so I&#39;m \
clearly biased here.<br><br>&gt; - we create extragear/plasma/ with subdirs for \
dataengines/, runners/,<br>&gt; applets/, plasmoids/, scriptengines/ and possibly \
animators/ (if any new <br>&gt; ones appear =). people move their own work as they \
want into<br>&gt; extragear/plasma/. plasmoids/ would house non-c++ packages. we will \
cover<br>&gt; which items to move over now at that irc meeting.<br>&gt;<br> &gt; - we \
create a place for sample applets; perhaps in extragear as well? e.g.<br>&gt; \
extragear/plasma/samples/ with all the subdirs under there? i don&#39;t want \
to<br>&gt; lose all the samples; i think they are valuable and should be maintained. \
<br>&gt; they shouldn&#39;t be installed, or shipped, by default but be there \
for<br>&gt; documentary and educational purposes.<br><br>Maybe it&#39;s better to \
keep them along the plasma libraries then? As a developer<br> I like to find the \
examples with the code of the library I&#39;m about to use<br>(phonon and solid \
follow this pattern).<br><br>&gt; - there will be *no* plasma stuff in kdeaddons. \
this could be seen as my<br>&gt; desire to kill kdeaddons outright, which would be \
accurate. ;) <br>&gt;<br>&gt; then releases will happen like this:<br>&gt;<br>&gt; - \
everything gets released with each KDE release, extragear \
included<br><br>w00t!<br><br>&gt; - we do a source only snapshot release of plasma \
itself for our more <br>&gt; devoted testers one a month. this is assuming KDE itself \
doesn&#39;t get into<br>&gt; this game so we don&#39;t have to.<br><br>Hmmm, reminds \
me something... :-p<br><br>&gt; but even if KDE as a whole doesn&#39;t do <br>&gt; \
periodic snapshots, i want to for plasma. maybe plasma could serve as a<br>&gt; test \
case here for the rest of KDE if need be<br><br>Looks fair.<br><br>&gt; - we do a \
snapshot release of extragear every 2 weeks, hopefully as proper <br>&gt; releases \
including binaries for as many platforms as possible. we need to<br>&gt; look into \
availability of services such as OpenSUSE&#39;s build system as i<br>&gt; really \
don&#39;t want to set up and maintain a network of systems ourselves =) \
<br><br>I&#39;m not sure about the 2 weeks thing, at this rate (and because of our \
current<br>organisation where we definitely don&#39;t branch enough) you&#39;ll end \
up<br>snapshoting non building or broken stuff.<br><br> Actually, the 1 month \
snapshot rate we discussed a while ago was my<br>pessimistic view because of our \
current way of working. If we had a SCM that<br>allows us to branch more (means cheap \
branching, fast switching, both way <br>merges that don&#39;t kill the history) then \
push changes in the main when ready<br>I&#39;d push to two weeks even for KDE \
itself.<br><br>&gt; what this means is that we can get people trying out new addons \
all the<br> &gt; time and keep the GHNS2 constantly repo fresh. it also means that \
kde<br>&gt; releases are full of all the plasma goodies up to that point in \
time.<br>&gt; hooray.<br><br>With regular snapshots like this you probably want to be \
able to separate <br>the &quot;stable build&quot;, from the &quot;snapshot \
builds&quot; when the user retrieves the<br>stuff. Does GHNS2 provide this kind of \
information? (I&#39;m really clueless<br>regarding GHNS2 features)<br><br>&gt; \
proposed irc meeting day: saturday sept 8th. please rsvp =) <br><br>Right, any time \
during the day? or you envision a 24h meeting? ;-)</blockquote><div><br>What, \
something wrong with that? Where are your hardcore feelings? <br><br><br>(sorry, but \
I couldn&#39;t resist. Usually, this is Wade&#39;s job, I know... Sorry to step on \
your toes, W!) <br></div><br><blockquote class="gmail_quote" style="border-left: 1px \
solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: \
1ex;">Regards.<br></blockquote></div><br>



_______________________________________________
Panel-devel mailing list
Panel-devel@kde.org
https://mail.kde.org/mailman/listinfo/panel-devel


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic