Hackage 2 blocking tickets

Hi all, FYI, I've been making tickets labelled 'hackage2' and 'important' for issues that we need to look at before migrating to Hackage2. The list is here: https://github.com/haskell/cabal/issues?labels=hackage2%2Cimportant&page=1&state=open Currently we have: * https://github.com/haskell/cabal/issues/1027 Migrate deprecations from Hackage1 * https://github.com/haskell/cabal/issues/1029 Improve user signup etc * https://github.com/haskell/cabal/issues/1030 Import user accounts from Hackage 1 * https://github.com/haskell/cabal/issues/1031 Rewrite to use SQL backend I don't think we're all agreed to do the SQL rewrite at the moment, but we should at least make a conscious decision about it. Thanks Ian

Hi Ian,
I created a ticket for hackage2. Should I mark it as such (but not
important)? Or will that interfere with this list?
Erik
On Fri, Sep 7, 2012 at 4:07 PM, Ian Lynagh
Hi all,
FYI, I've been making tickets labelled 'hackage2' and 'important' for issues that we need to look at before migrating to Hackage2.
The list is here: https://github.com/haskell/cabal/issues?labels=hackage2%2Cimportant&page=1&state=open
Currently we have: * https://github.com/haskell/cabal/issues/1027 Migrate deprecations from Hackage1 * https://github.com/haskell/cabal/issues/1029 Improve user signup etc * https://github.com/haskell/cabal/issues/1030 Import user accounts from Hackage 1 * https://github.com/haskell/cabal/issues/1031 Rewrite to use SQL backend
I don't think we're all agreed to do the SQL rewrite at the moment, but we should at least make a conscious decision about it.
Thanks Ian
_______________________________________________ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel

Hi Erik, On Fri, Sep 07, 2012 at 04:22:24PM +0200, Erik Hesselink wrote:
I created a ticket for hackage2. Should I mark it as such (but not important)? Or will that interfere with this list?
Definitely mark it hackage2. Mark it important if you think that it needs to be fixed before we migrate to Hackage2. Thanks Ian

On Fri, Sep 7, 2012 at 4:28 PM, Ian Lynagh
On Fri, Sep 07, 2012 at 04:22:24PM +0200, Erik Hesselink wrote:
I created a ticket for hackage2. Should I mark it as such (but not important)? Or will that interfere with this list?
Definitely mark it hackage2. Mark it important if you think that it needs to be fixed before we migrate to Hackage2.
Hmm, apparently I can't add labels. It's issue 1028. I don't think it's important to fix before migrating, but it would be nice if someone with privileges could label it. Erik

On Fri, Sep 07, 2012 at 03:54:08PM +0100, Erik Hesselink wrote:
Hmm, apparently I can't add labels. It's issue 1028. I don't think it's important to fix before migrating, but it would be nice if someone with privileges could label it.
The issue there is mishandling unknown repository types, here "github" instead of "git".

On Fri, Sep 07, 2012 at 04:54:08PM +0200, Erik Hesselink wrote:
On Fri, Sep 7, 2012 at 4:28 PM, Ian Lynagh
wrote: On Fri, Sep 07, 2012 at 04:22:24PM +0200, Erik Hesselink wrote:
I created a ticket for hackage2. Should I mark it as such (but not important)? Or will that interfere with this list?
Definitely mark it hackage2. Mark it important if you think that it needs to be fixed before we migrate to Hackage2.
Hmm, apparently I can't add labels.
Oh, OK; I've tagged it 'hackage2'. Thanks Ian
participants (3)
-
Erik Hesselink
-
Ian Lynagh
-
Ross Paterson