question about uploads of code contribution
Hello, 1) I want to upload a version with minor changes. Should I send out an "announcement"? 2) does the hackage database have a "reader/writer" lock to protect readers, i.e. people downloading when I am uploading? Regards, Vasili
At Fri, 22 Aug 2008 00:29:40 -0500, Galchin, Vasili wrote:
2) does the hackage database have a "reader/writer" lock to protect readers, i.e. people downloading when I am uploading?
1. new versions must have a different version number 2. the version number is in the tarball name therefore: 3. uploading a new version is a non-destructive operation and will not affect anyone downloading older versions. At least, that is my understanding. j.
ahhh ... makes perfect sense vis-a-vis the read/write problem Jeremy.
Hopefully using an incremented version number is enforced via the hackage
database!! ;^)
Vasili
On Fri, Aug 22, 2008 at 12:55 AM, Jeremy Shaw
At Fri, 22 Aug 2008 00:29:40 -0500, Galchin, Vasili wrote:
2) does the hackage database have a "reader/writer" lock to protect readers, i.e. people downloading when I am uploading?
1. new versions must have a different version number 2. the version number is in the tarball name
therefore:
3. uploading a new version is a non-destructive operation and will not affect anyone downloading older versions.
At least, that is my understanding.
j.
Hi
1) I want to upload a version with minor changes. Should I send out an "announcement"?
How minor are the changes? I tend to annouce no more than once every few months for a package, and when its popular or has new features people might be interested in (I am assuming this is a package you wrote in the first place and uploaded last time? If not, you probably shouldn't be uploading it) Thanks Neil
participants (3)
-
Galchin, Vasili -
Jeremy Shaw -
Neil Mitchell