coapp-developers team mailing list archive

[Tim Rogers <tiroger@xxxxxxxxxxxxx>]

By the same token, releasing early makes the assumption that significant portions of the software in question are believed to operate correctly unless stated otherwise.  We could absolutely release CoApp "early" in its present state, but I would only wish to do so with a disclaimer that we do not believe the software to be functioning properly at this time.

I, at least, am not willing to promise that it won't light your computer on fire if you try using it right now.  I don't think it will, but I really can't make that promise.  Nor can I promise that it will do anything that it is supposed to until we have had a chance to seriously look it over first.

With all of this in mind, if you would like to build it yourself and try using the tools to construct packages and install them, I'd be happy to get input from test systems outside my control.  Just don't blame us if the system becomes unstable.

-Tim

From: coapp-developers-bounces+tiroger=microsoft.com@xxxxxxxxxxxxxxxxxxx [mailto:coapp-developers-bounces+tiroger=microsoft.com@xxxxxxxxxxxxxxxxxxx] On Behalf Of Charles Strahan
Sent: Tuesday, October 04, 2011 8:09 PM
To: coapp-developers@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Coapp-developers] First useful pkgs? (libz, libpng)

I think that Garret is suggesting that CoApp isn't yet ready to be released for the common user, in the same manner that one wouldn't deploy a 50% working (or 50% broken) web site.

My understanding is that "Release Early, Release Often" applies to projects that are 100% working - although perhaps not 100% feature complete. I could be wrong, but it would seem that CoApp isn't 100% solid yet.

I'm guessing that "Release Early, Release Often" will be the next logical step after the first release.

-Charles

On Tue, Oct 4, 2011 at 11:53 AM, Olaf van der Spek <olafvdspek@xxxxxxxxx<mailto:olafvdspek@xxxxxxxxx>> wrote:
On Thu, Sep 29, 2011 at 4:20 PM, Garrett Serack <garretts@xxxxxxxxxxxxx<mailto:garretts@xxxxxxxxxxxxx>> wrote:
> *sigh*
>
> Software Developers  use "Release Early, Release Often". It's not just an open source idea.
>
> And yes, that would be ideal.
>
> However, We're still at a stage where releasing something would be completely pointless.
>
> Every blocking bug that I have yet to resolve means that no matter what I've got, you can't use it.
>
> Release Early, Release Often works ok for Applications with a gradually increasing feature-set
Isn't coapp such software? I'm sure it's possible to define such a feature-set.

Olaf

_______________________________________________
Mailing list: https://launchpad.net/~coapp-developers
Post to     : coapp-developers@xxxxxxxxxxxxxxxxxxx<mailto:coapp-developers@xxxxxxxxxxxxxxxxxxx>
Unsubscribe : https://launchpad.net/~coapp-developers
More help   : https://help.launchpad.net/ListHelp