Deprecating distributed-process-platform
19 views
Skip to first unread message
Tim Watson
Dec 30, 2014, 5:51:30 PM12/30/14
to cloud-haskel...@googlegroups.com
Now that -platform has been split up into smaller chunks, I'm thinking of deprecating the package and github repo. This will involve moving the git repo to the https://github.com/haskell-distributed-deprecated organisation. I'm not deleting it as there's pre-split work in progress I'll want to salvage later on.
Any objections or suggestions about this before I go ahead?
Cheers,
Cheers,
Tim
Tim Watson
Dec 31, 2014, 4:14:38 AM12/31/14
to Boespflug, Mathieu, cloud-haskel...@googlegroups.com
Hi Mathieu,
Ok thanks for the recommendation. I'll do that for the time being.
Cheers,
Tim
On 31 December 2014 at 08:26, Boespflug, Mathieu <m...@tweag.io> wrote:
It's something of an inconvenience for people that still depend on
distributed-process-platform for whatever reason (and there still are
reasons to do so since not everything has been salvaged yet) that they
now need to pull from elsewhere and so need to manually modify all
their .git/config's. I'm not convinced an extra github org is
necessary. I would simply keep the package at its existing location,
not rename it, and just mark prominently that it is a deprecated
package (i.e. in the Github repo description line, on Hackage using
the proper mechanism for deprecation, and in the README.md that Github
shows).
--
Mathieu Boespflug
Founder at http://tweag.io.
> --
> You received this message because you are subscribed to the Google Groups
> "cloud-haskell-developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to cloud-haskell-deve...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
Boespflug, Mathieu
Jan 13, 2015, 7:29:26 AM1/13/15
to Tim Watson, cloud-haskel...@googlegroups.com
It's something of an inconvenience for people that still depend on
distributed-process-platform for whatever reason (and there still are
reasons to do so since not everything has been salvaged yet) that they
now need to pull from elsewhere and so need to manually modify all
their .git/config's. I'm not convinced an extra github org is
necessary. I would simply keep the package at its existing location,
not rename it, and just mark prominently that it is a deprecated
package (i.e. in the Github repo description line, on Hackage using
the proper mechanism for deprecation, and in the README.md that Github
shows).
--
Mathieu Boespflug
Founder at http://tweag.io.
On 31 December 2014 at 00:51, Tim Watson <watson....@gmail.com> wrote:
distributed-process-platform for whatever reason (and there still are
reasons to do so since not everything has been salvaged yet) that they
now need to pull from elsewhere and so need to manually modify all
their .git/config's. I'm not convinced an extra github org is
necessary. I would simply keep the package at its existing location,
not rename it, and just mark prominently that it is a deprecated
package (i.e. in the Github repo description line, on Hackage using
the proper mechanism for deprecation, and in the README.md that Github
shows).
--
Mathieu Boespflug
Founder at http://tweag.io.
On 31 December 2014 at 00:51, Tim Watson <watson....@gmail.com> wrote:
Reply all
Reply to author
Forward
0 new messages