coapp-developers team mailing list archive

[Garrett Serack <garretts@xxxxxxxxxxxxx>]

*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, or software that is mature enough that you can incrementally add features.

It's pretty trivial at this point to build CoApp (install VS2010, WindowsSDK, git, and  download https://github.com/downloads/coapp/checkout/coapp-src.cmd , and run it) I'd be more than happy to take pull requests for code contributions to speed up the process.



-----Original Message-----
From: Olaf van der Spek [mailto:olafvdspek@xxxxxxxxx] 
Sent: Wednesday, September 28, 2011 10:08 AM
To: Garrett Serack
Cc: coapp-developers@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Coapp-developers] First useful pkgs? (libz, libpng)

On Mon, Sep 26, 2011 at 10:33 PM, Garrett Serack <garretts@xxxxxxxxxxxxx> wrote:
> We had some packages when we pushed out the first beta; I've since removed them because they'll be incompatible with beta 2, which we should be publishing the end of next week (Tim the Tester is on his honeymoon this week, so we're not going to release anything when the tester is away).

Most open source projects use a release early, release often model.
Wouldn't this be suitable for coapp too?

Olaf