Three major releases in 24 hours.

Question

Three major releases in 24 hours.

phadej opened this issue 5 years ago · comments

Please, sleep over the releases. No need to spam Hackage.

(edit: only three are in rapid succession, the first one is already two days ago...)

David Johnson · Answer 1 · Thu Nov 07 2019 03:25:08 GMT+0800 (China Standard Time)

@phadej the public interface is changing, a major version bump is required to abide by PVP. Surely hackage can handle 3 POST requests.

David Johnson · Answer 2 · Thu Nov 07 2019 03:27:36 GMT+0800 (China Standard Time)

@phadej, amazonka uploads 60 packages at a time, I think we're ok here.

Oleg Grenrus · Answer 3 · Thu Nov 07 2019 03:29:38 GMT+0800 (China Standard Time)

Hackage is permanent store, it’s one upload but the version is there forever. You can only upload a package version once and this cannot be undone, so try to get it right the first time! You could have made only single major release instead of three. Please rethink your release process taking unique Hackage coat model into account.

…

On 6 Nov 2019, at 21.25, David Johnson ***@***.***> wrote: @phadej the public interface is changing, a major version bump is required to abide by PVP. Surely hackage can handle 3 POST requests. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

Oleg Grenrus · Answer 4 · Thu Nov 07 2019 03:30:40 GMT+0800 (China Standard Time)

Amazonka maintainers are not uploading new versions of the same package in short time.

…

Sent from my iPhone

On 6 Nov 2019, at 21.27, David Johnson ***@***.***> wrote: @phadej, amazonka uploads 60 packages at a time, I think we're ok here. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

David Johnson · Answer 5 · Thu Nov 07 2019 03:36:22 GMT+0800 (China Standard Time)

Thanks for your recommendation.

David Johnson · Answer 6 · Thu Nov 07 2019 03:43:05 GMT+0800 (China Standard Time)

@phadej Also, I noticed when I try to upload the documentation standalone that it doesn't work. Hackage will fail to build this package because it doesn't have the third party libraries, so I have to upload the docs manually.

Maybe this is what you're referring to ? I'm trying to upload docs here.

cabal upload -d arrayfire-0.4.0.0-docs.tar.gz --publish

But yes, if there's any way you guys can fix hackage to allow documentation pushes, that would be great. It did work for 0.2.0.0 though. Not sure what's happening now. But how I release packages publicly shouldn't be dictated by hackage's data store. Hackage also has a deprecation option as well for that, if need be.

Oleg Grenrus · Answer 7 · Thu Nov 07 2019 03:44:43 GMT+0800 (China Standard Time)

Try with web interface https://hackage.haskell.org/package/arrayfire-0.4.0.0/maintain/docs, it works but cabal doesn't it's a bug in cabal-install. Please report it then to its issue tracker.

David Johnson · Answer 8 · Thu Nov 07 2019 03:45:24 GMT+0800 (China Standard Time)

The granularity of the changes that are batched into a release can be debated, but I'd leave that to the package author's discretion, who should take into account end user's timeline for the needed feature.

David Johnson · Answer 9 · Thu Nov 07 2019 03:45:31 GMT+0800 (China Standard Time)

Thanks, will give the web API a go.

Oleg Grenrus · Answer 10 · Thu Nov 07 2019 03:48:24 GMT+0800 (China Standard Time)

I hope that those mentioned end users will donate to Haskell.org which resources are used to host hackage.haskell.org

David Johnson · Answer 11 · Thu Nov 07 2019 04:19:12 GMT+0800 (China Standard Time)

@phadej So I was able to use the web API to upload documentation, but it doesn't seem to show up on the hackage page. Is there a way I can see any kind of logs as to what the issue might be?

David Johnson · Answer 12 · Mon Nov 11 2019 23:37:39 GMT+0800 (China Standard Time)

@phadej was able to get haddocks uploaded thanks to @cocreature. For all further PSA (public service announcements) regarding hackage and its cost model, I think this would be better served as a haskell-cafe message so it can benefit the entire community since it seems everybody is at risk. Going forward let's keep this public issue tracker related to ArrayFire issues only. Thanks!