On Wed, Apr 6, 2011 at 1:55 PM, Igor Stasenko <[email protected]> wrote:
> ---------- Forwarded message ---------- > From: Igor Stasenko <[email protected]> > Date: 6 April 2011 13:55 > Subject: Re: [Pharo-project] Actions done in 1.3 > To: laurent laffont <[email protected]> > > > On 6 April 2011 10:30, laurent laffont <[email protected]> wrote: > > > > On Wed, Apr 6, 2011 at 10:17 AM, Igor Stasenko <[email protected]> > wrote: > >> > >> Planning is also important. > >> > >> Time is good, but another thing is i think we should think about, > >> what features we want to be in new release, and do not release until > >> they delivered. > > > > I don't really like this. I prefer rhythm, agility. Timeboxing enables > > maximum value in each release. If a feature is really important, it will > be > > on time. If not on time, it means it was no so important. > > Always green test is a must-have. > > > >> > >> Besides bug fixing and minor improvements, there should be some > >> functionality which we want to have in new release, > > > > That should be a goal, but don't delay a release because the feature is > not > > here. If releases are often ( for example every 3 months), shorter, it > won't > > be a big problem to wait for the next one. > > I prefer to have a release *now* without my feature and wait 3 months for > > the next release than no release and waiting for 3 months more with less > and > > less energy. > > > > But you don't have to wait, if you want to stay on bleeding edge, you > know how to do that. > Just go to hudson and dowload freshly built 1.3 image. > I won't do this for production. We need a officially released image. Because if you can pick any image at any moment and declare it new release, > then i don't understand why do we need releases at all? > Because people build applications / frameworks they declare compatible with a fixed version of Pharo. > What makes release to be release , when you can download latest > version at any moment? > The date :) Ubuntu is released every 6 months. That gives a rhythm. Integrates new stuff, freeze, release. Same for Gnome and KDE. Linux kernel has a 2 weeks merge window then go rc. We have learned the benefits of fixed iteration with agile methods & extreme programming. > That's why i saying that from release to release cleanup and fixes is > good, but there should be some major functional changes, > which worth to be labeled as a new version. > And if you don't have them, then there is no point to make a release. > In three months there's a lot of stuff which enters Pharo. That's enough for me to justify a release and get feedback from users. Laurent. > > > Laurent. > > > > > -- > Best regards, > Igor Stasenko AKA sig. > > > > -- > Best regards, > Igor Stasenko AKA sig. > >
