Re: [Haskell-cafe] Checking in packages to Hackage early in development cycle?

On 2009 Mar 19, at 12:30, Colin Paul Adams wrote:

...

...

...

...

...

"Max" == Max Rabkin writes:

Max> On Thu, Mar 19, 2009 at 4:41 PM, Manlio Perillo Max> wrote:

Max> Personally, I think that there is little harm in releasing a Max> package if it does something useful in a not-totally-broken Max> way. Especially if you plan to extend it.

Suppose you intend to extend it, and are not sure yet if the interface will change as a result?

Generally you indicate this by changing the minor version: 0.3.0, 0.3.1, etc. have compatible APIs, but 0.4.0 has an incompatible API. And with major version 0, API breakage is expected in new releases. -- brandon s. allbery [solaris,freebsd,perl,pugs,haskell] allbery@kf8nh.com system administrator [openafs,heimdal,too many hats] allbery@ece.cmu.edu electrical and computer engineering, carnegie mellon university KF8NH