Tracking bugs for libraries
Simon Peyton Jones
simonpj at microsoft.com
Wed May 6 09:45:02 UTC 2015
well, according to the page, Hoopl would come under clause (3) of what a “core library” is; GHC depends on it.
So yes, it should be in the table.
Simon
From: ghc-devs [mailto:ghc-devs-bounces at haskell.org] On Behalf Of Edward Kmett
Sent: 06 May 2015 07:48
To: Jan Stolarek
Cc: ghc-devs at haskell.org
Subject: Re: Tracking bugs for libraries
Hoopl didn't exist when the page was first created. I'm not sure if it should be considered a "core library" or not, honestly. If so, then it probably belongs on that page. If not, then it is probably worth documenting more clearly somewhere where its issues are tracked.
-Edward
On Wed, May 6, 2015 at 1:53 AM, Jan Stolarek <jan.stolarek at p.lodz.pl<mailto:jan.stolarek at p.lodz.pl>> wrote:
> As of a couple of months ago, we updated
>
> https://wiki.haskell.org/Library_submissions
>
> to include the definitive source for where issues should be tracked on a
> package by package basis for all of the core libraries. As we spread
> maintainership of these packages around, we found more and more people
> preferred using github issue tracking to the legacy trac.
That makes perfect sense. Thanks for clarifying. However, Hoopl is not included on the wiki page.
Is that accidental or intentional omission?
Janek
>
> There may well wind up with parallel trac items for some items in a
> separate project issue tracker, but the primary reason for such would be
> when ghc has to respond to an external change. Most (if not all) of the
> remaining duplicate issues were pushed out to the corresponding external
> trackers.
>
> As we clear out the remaining issues, we might look at removing these as
> component selections in the trac.
>
> -Edward
>
> > Janek
> >
> > ---
> > Politechnika Łódzka
> > Lodz University of Technology
> >
> > Treść tej wiadomości zawiera informacje przeznaczone tylko dla adresata.
> > Jeżeli nie jesteście Państwo jej adresatem, bądź otrzymaliście ją przez
> > pomyłkę prosimy o powiadomienie o tym nadawcy oraz trwałe jej usunięcie.
> >
> > This email contains information intended solely for the use of the
> > individual to whom it is addressed. If you are not the intended recipient
> > or if you have received this message in error, please notify the sender
> > and delete it from your system.
> > _______________________________________________
> > ghc-devs mailing list
> > ghc-devs at haskell.org<mailto:ghc-devs at haskell.org>
> > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
---
Politechnika Łódzka
Lodz University of Technology
Treść tej wiadomości zawiera informacje przeznaczone tylko dla adresata.
Jeżeli nie jesteście Państwo jej adresatem, bądź otrzymaliście ją przez pomyłkę
prosimy o powiadomienie o tym nadawcy oraz trwałe jej usunięcie.
This email contains information intended solely for the use of the individual to whom it is addressed.
If you are not the intended recipient or if you have received this message in error,
please notify the sender and delete it from your system.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-devs/attachments/20150506/a4a69185/attachment-0001.html>
More information about the ghc-devs
mailing list