Containers -- how to synchronize development and lagging repo

Milan Straka fox at
Wed Jun 15 10:16:01 CEST 2011

Hi Edward and all,

> Hello Milan,
> We currently have a lagging repository system setup for Hoopl described
> here:
> maybe it is applicable for the containers process?  It does, however,
> predate the switch to Git, and it's possible that just using multiple branches
> might also bean option.

so it seems it is the responsibility of the maintainers to push to the
lagging repo and do the GHC validation?

Can we also release the cabal packages? Should the numbering of the
package somehow correspond to the GHC releases?


> Edward
> Excerpts from Milan Straka's message of Fri Jun 10 08:11:59 -0400 2011:
> > Hi GHC HQ,
> > 
> > with the new library submission process, I think we should have
> > development repo for containers (maybe on github?).
> > 
> > Is there any standard way of dealing with lagging repos? I am not sure
> > if updating the lagging repo and releasing cabal packages is
> > responsibility of GHC HQ of the maintainers. With the new library
> > process, there will probably be more people affected by this issue.
> > 
> > BTW, we can also do the development on different branch of the repo,
> > or the lagging repo can be a different branch. But it sounds a bit
> > tricky...
> > 
> > Cheers,
> > Milan
> > 

More information about the Libraries mailing list