Should we continue to keep all the projects in one repository

[Tim Watson]

I've posted an issue at https://github.com/haskell-distributed/distributed-process/issues/120 about this, but I'm increasingly aware that some 'traffic' is probably best discussed outside of the github issue tracker.

It seems a bit awkward (to me, at least) figuring out what's changed since the last tag for project-XYZ when we have multiple packages bundled into the same repository. On the other hand, I can see that there are some administrative advantages and, of course, it's easier when hacking on more than one project.

If it was up to me, I'd be inclined to split up the different projects into their own repositories. I am not however going to do anything radical without getting agreement for the other maintainers. So, comments on a postcard please....

[Rodlogic]

Tim,

For what is worth, I am also inclined to see these projects split up. Splitting does add a certain overhead when working across projects, but the benefits are worth it, imo. We can tackle this added overhead looking for ways to automate mundane dev tasks (e.g. cloud-haskell umbrella project/scripts that you already created).

[Tim Watson]

On 5 Feb 2013, at 00:00, Rodlogic <ad...@rodlogic.net> wrote:

Tim,

For what is worth, I am also inclined to see these projects split up. Splitting does add a certain overhead when working across projects, but the benefits are worth it, imo. We can tackle this added overhead looking for ways to automate mundane dev tasks (e.g. cloud-haskell umbrella project/scripts that you already created).

Exactly. I'm not going to go too far with clever automation right now, but at some stage it'll be worth doing some things to make ci builds on topic branches work across projects.

On that note - the repos are split and I'll be finishing off a few things tonight we should be announced by wed morning.

Cheers

Tim

On Friday, January 25, 2013 9:31:42 AM UTC-2, Tim Watson wrote:

I've posted an issue at https://github.com/haskell-distributed/distributed-process/issues/120 about this, but I'm increasingly aware that some 'traffic' is probably best discussed outside of the github issue tracker.

It seems a bit awkward (to me, at least) figuring out what's changed since the last tag for project-XYZ when we have multiple packages bundled into the same repository. On the other hand, I can see that there are some administrative advantages and, of course, it's easier when hacking on more than one project.

If it was up to me, I'd be inclined to split up the different projects into their own repositories. I am not however going to do anything radical without getting agreement for the other maintainers. So, comments on a postcard please....

--
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/groups/opt_out.