[GHC DevOps Group] FreeBSD in Tier 1

[Manuel M T Chakravarty]

[RESENT MESSAGE — see https://mail.haskell.org/pipermail/ghc-devops-group/2017-October/000004.html]


Yes, and we have got options for that, such as cross-compiling and using QEMU. We will cross that bridge when we get to it.

For now, please let us focus on our immediate goal of automatically producing build artefacts to streamline the release process and for providing reliable CI for the core platforms.

Given the CircleCI config Mathieu already contributed, what is missing to create the release artefacts on CircleCI? 

Cheers,
Manuel

> Ben Gamari <ben at well-typed.com <mailto:ben at well-typed.com>>:
> Manuel M T Chakravarty <manuel.chakravarty at tweag.io <mailto:manuel.chakravarty at tweag.io>> writes:
>> Simon, Ben, this sounds to me very much like a Tier 2 commitment. May
>> I suggest that we classify FreeBSD as Tier 2 until somebody else comes
>> along who can commit to actively maintaining the platform and provide
>> timely fixes (starting with fixing the current problems)?
>> 
> Yes, I agree and am fine with moving FreeBSD to tier 2 status.
> 
> However, I would like to nevertheless emphasize the point I raised
> earlier about cross-platform CI: If and when a maintainer picks up
> FreeBSD (or any other Tier 2 platform) our infrastructure should be able
> to accomodate them.
> 
> For instance, I imagine Moritz will move to make AArch64 Tier 1 soon
> after he stabilizes that platform.
> 
> Cheers,
> 
> - Ben

_______________________________________________
Ghc-devops-group mailing list
Ghc-devops-group at haskell.org
https://haskell.org/cgi-bin/mailman/listinfo/ghc-devops-group
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://haskell.org/pipermail/ghc-devops-group/attachments/20171010/136a9400/attachment-0001.html>