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

List:       kde-active
Subject:    Re: "Big picture" design one release cycle ahead?
From:       Thomas Pfeiffer <colomar () autistici ! org>
Date:       2012-10-27 19:58:38
Message-ID: 1496546.TbK79uDxb1 () rabbit
[Download RAW message or body]

On Saturday 27 October 2012 18:37:56 Aaron J. Seigo wrote:
> On Saturday, October 27, 2012 10:55:37 Bj=F6rn Balazs wrote:
> > We would probably need dot releases after each sprint (and hence have
> > a shippable product after each sprint)
> =

> doing a proper release after each sprint will kill our productivity due to
> the amount of developer manpower we have available to us. thankfully,
> releases should not be necessary as people can simply update their tablet
> in-situ using zypper. so we can simply refresh the build repos on OBS so
> those who are participating with us can follow development.

Agreed. We won't need proper releases with all the fuzz. That's the big plu=
s =

of having an always releasable master: When we work with users, we can just =

ask them to zypper up from master without risking the loss of data / cats / =

hamsters / grandmas.

> > and we would need to implement
> > some way of talking to the users (best would probably be directly
> > through the product).
> =

> do you have a concrete concept of what this might look like?

From my perspective, ideally we'd have a group of users interested in =

participation (but not necessarily programming) who we interview and do =

usability tests and surveys with etc.
_______________________________________________
Active mailing list
Active@kde.org
https://mail.kde.org/mailman/listinfo/active
[prev in list] [next in list] [prev in thread] [next in thread]