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

Brandon S. Allbery KF8NH allbery at ece.cmu.edu
Thu Mar 19 12:39:02 EDT 2009

On 2009 Mar 19, at 12:30, Colin Paul Adams wrote:
>>>>>> "Max" == Max Rabkin <max.rabkin at gmail.com> writes:
>    Max> On Thu, Mar 19, 2009 at 4:41 PM, Manlio Perillo
>    Max> <manlio_perillo at libero.it> 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 at kf8nh.com
system administrator [openafs,heimdal,too many hats] allbery at ece.cmu.edu
electrical and computer engineering, carnegie mellon university    KF8NH

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
Url : http://www.haskell.org/pipermail/haskell-cafe/attachments/20090319/fe17963d/PGP.bin

More information about the Haskell-Cafe mailing list