Re: Tentative high-level plans for 7.10.1
On Fri, Oct 3, 2014 at 11:35 PM, Austin Seipp wrote: > - Cull and probably remove the 7.8.4 milestone. >- Simply not enough time to address almost any of the tickets > in any reasonable timeframe before 7.10.1, while also shipping them. >- Only one, probably workarouadble, not game-changing > bug (#9303) marked for 7.8.4. >- No particular pressure on any outstanding bugs to release immediately. >- ANY release would be extremely unlikely, but if so, only > backed by the most critical of bugs. >- We will move everything in 7.8.4 milestone to 7.10.1 milestone. > - To accurately catalogue what was fixed. > - To eliminate confusion. > #8960 looks rather serious and potentially makes all of 7.8 a no-go for some users. I'm worried that we're (in general) pushing too many bug fixes towards future major versions. Since major versions tend to add new bugs, we risk getting into a situation where no major release is really solid. ___ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs
Re: Tentative high-level plans for 7.10.1
Austin Seipp writes: snip. > > We do not believe we will ship a 7.8.4 at all, contrary to what you > may have seen on Trac - we never decided definitively, but there is > likely not enough time. Over the next few days, I will remove the > defunct 7.8.4 milestone, and re-triage the assigned tickets. > The only potential issue here is that not a single 7.8 release will be able to bootstrap LLVM-only targets due to #9439. I'm not sure how much of an issue this will be in practice but there should probably be some discussion with packagers to ensure that 7.8 is skipped on affected platforms lest users be stuck with no functional stage 0 compiler. Cheers, - Ben pgpjQud6SuAQv.pgp Description: PGP signature ___ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs
Tentative high-level plans for 7.10.1
Hi *, Today, Mikolaj and I discussed and plotted out a quick, high-level roadmap for the 7.10.1 release, based on our earlier plans. Consider this the 10,000 foot view (the last one was like a view from space). **The TL;DR** - We think the freeze and branching for major things will happen in _5 to 6 weeks from now_, in early/mid November. The release will happen in Feburary. Developers, please read some code (see below), and get your stuff in! The initial bug list will come next week for you to look at. --- The not-quite-TL;DR version: We'll get about 4 months of fixes into STABLE. This stability period will come at a typically low-point during the year, when many people will be preoccupied with Holidays. So, we're trying to aim far ahead, and try to give STABLE a long, official 'cooking period'. Feature inclusions after the freeze _are_ negotiable, but not large changes. Expect us to say "No" more often this time around. The STABLE branch will only be touchable by me and Herbert. We do not believe we will ship a 7.8.4 at all, contrary to what you may have seen on Trac - we never decided definitively, but there is likely not enough time. Over the next few days, I will remove the defunct 7.8.4 milestone, and re-triage the assigned tickets. We don't have any expected time for an RC just yet. I will spend the next few days culling the 7.10.1 milestone to contain appropriate tickets. Expect a list of these tickets early next week, with more info. Developers: if you have time, **please** review some code, and get your stuff in too! Petition people to review things of yours. Review things other people wrote, and learn new stuff. High five each other afterwords. Here are the major patches on Phabricator still needing review, that I think we'd like to see for 7.10.1: - D168: Partial type signatures - D72: New rebindable syntax for arrows. - D155: LLVM 3.5 compatibility - D169: Source code note infrastructure - D202: Injective type families - Edward Yang's HEAP_ALLOCED saga, D270 through D293 - D130: Implementation of hsig (module signatures) It is possible not all of these will make it. But I think they're solid priorities to try and land soon. Please let me know if you disagree with this. After I publish the bug list, please also take a look, and use your judgement to include or remove things you think are sensible for 7.10.1 (I trust your judgement, and we can always talk it out later). I think that's all. Here's a full roadmap below from our notes: --- - Expected ETA for 7.10.1: - Roughly Feburary 2015. - Expected code freeze ~5wks - Entails making the stable branch - Tentatively create branch on Nov. 7th. - ~3-4mo's of freeze time for STABLE. - Empirically a low-point in development due to Holidays, but gives us a lot of time. - Cull and probably remove the 7.8.4 milestone. - Simply not enough time to address almost any of the tickets in any reasonable timeframe before 7.10.1, while also shipping them. - Only one, probably workarouadble, not game-changing bug (#9303) marked for 7.8.4. - No particular pressure on any outstanding bugs to release immediately. - ANY release would be extremely unlikely, but if so, only backed by the most critical of bugs. - We will move everything in 7.8.4 milestone to 7.10.1 milestone. - To accurately catalogue what was fixed. - To eliminate confusion. - Cull the 7.10.1 milestone - Currently ~700 tickets. - 31 high tickets. - 1 highest priority ticket. - Bulk of them will need moved out to 7.12.1. - Ask developers/users to move things back in. - Demote any old tickets out of highest according to bug tracker policy. - Alert people these are our priorities. - Go through ONLY high/highest priority tickets for 7.10.1. - Email ghc-devs with plans. - Major tentative patches for 7.10 - D168: Partial type signatures - D72: New rebindable syntax for arrows. - D155: LLVM 3.5 compatibility (not big, but important for users!) - D169: Source code note infrastructure (partially reviewed, Austin to review) - D202: Injective type families - Edward Yang's HEAP_ALLOCED saga, D270 through D293 - D130: Implementation of hsig (module signatures) -- Regards, Austin Seipp, Haskell Consultant Well-Typed LLP, http://www.well-typed.com/ ___ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs
Re: Windows build broken (again)
Python 3 is a likely culprit (though I couldn't confirm it), so I reverted it. Does it work now? On Fri, Oct 3, 2014 at 5:51 PM, Herbert Valerio Riedel wrote: > On 2014-10-03 at 17:29:31 +0200, Simon Peyton Jones wrote: > > Perhaps, yes, it is Python 3. I don't know. Could someone revert to > > make it work again, please? > > Fyi, I can't reproduce this specific problem on Cygwin at least (I don't > have any working pure Msys2 environment yet (still working on it), as > this may exactly be the kind of failure I'd expect Msys2 to be prone to > while Cygwin to be unaffected by). > > What I tried in order to reproduce: > > $ git rev-parse HEAD > 084d241b316bfa12e41fc34cae993ca276bf0730 # <-- this is the > Py3/testsuite commit > > $ make TEST=tc012 WAY=normal > ... > => tc012(normal) 3039 of 4088 [0, 0, 0] > cd ./typecheck/should_compile && > 'C:/cygwin64/home/ghc/ghc-hvr/inplace/bin/ghc-stage2.exe' -fforce-recomp > -dcore-lint -dcmm-lint -dno-debug-output -no-user-package-db -rtsopts > -fno-ghci-history -c tc012.hs -fno-warn-incomplete-patterns > >tc012.comp.stderr 2>&1 > > OVERALL SUMMARY for test run started at Fri Oct 3 15:42:04 2014 GMT >0:00:03 spent to go through > 4088 total tests, which gave rise to > 12360 test cases, of which > 12359 were skipped > > 0 had missing libraries > 1 expected passes > 0 expected failures > ... > > > And btw, with the latest GHC HEAD commit (and I suspect the recent > HEAP_ALLOCED-related commits to be responsible for that), I get a ton of > testsuite failures due to such errors: > > T8639_api.exe: Unknown PEi386 section name `staticclosures' (while > processing: > C:\cygwin64\home\ghc\ghc-hvr\libraries\ghc-prim\dist-install\build\HSghcpr_BE58KUgBe9ELCsPXiJ1Q2r.o) > > ___ > ghc-devs mailing list > ghc-devs@haskell.org > http://www.haskell.org/mailman/listinfo/ghc-devs > ___ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs
Re: Windows build broken (again)
On 2014-10-03 at 17:29:31 +0200, Simon Peyton Jones wrote: > Perhaps, yes, it is Python 3. I don't know. Could someone revert to > make it work again, please? Fyi, I can't reproduce this specific problem on Cygwin at least (I don't have any working pure Msys2 environment yet (still working on it), as this may exactly be the kind of failure I'd expect Msys2 to be prone to while Cygwin to be unaffected by). What I tried in order to reproduce: $ git rev-parse HEAD 084d241b316bfa12e41fc34cae993ca276bf0730 # <-- this is the Py3/testsuite commit $ make TEST=tc012 WAY=normal ... => tc012(normal) 3039 of 4088 [0, 0, 0] cd ./typecheck/should_compile && 'C:/cygwin64/home/ghc/ghc-hvr/inplace/bin/ghc-stage2.exe' -fforce-recomp -dcore-lint -dcmm-lint -dno-debug-output -no-user-package-db -rtsopts -fno-ghci-history -c tc012.hs -fno-warn-incomplete-patterns >tc012.comp.stderr 2>&1 OVERALL SUMMARY for test run started at Fri Oct 3 15:42:04 2014 GMT 0:00:03 spent to go through 4088 total tests, which gave rise to 12360 test cases, of which 12359 were skipped 0 had missing libraries 1 expected passes 0 expected failures ... And btw, with the latest GHC HEAD commit (and I suspect the recent HEAP_ALLOCED-related commits to be responsible for that), I get a ton of testsuite failures due to such errors: T8639_api.exe: Unknown PEi386 section name `staticclosures' (while processing: C:\cygwin64\home\ghc\ghc-hvr\libraries\ghc-prim\dist-install\build\HSghcpr_BE58KUgBe9ELCsPXiJ1Q2r.o) ___ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs
RE: Windows build broken (again)
Perhaps, yes, it is Python 3. I don't know. Could someone revert to make it work again, please? Simon From: ghc-devs [mailto:ghc-devs-boun...@haskell.org] On Behalf Of Simon Peyton Jones Sent: 02 October 2014 21:40 To: ghc-devs@haskell.org Subject: Windows build broken (again) Sigh. The testsuite fails utterly on Windows, with thousands of identical errors => tc012(normal) 3039 of 4088 [1, 2677, 88] cd .\typecheck\should_compile && 'C:/code/HEAD/inplace/bin/ghc-stage2.exe' -fforce-recomp -dcore-lint -dcmm-lint -dno-debug-output -no-user-package-db -rtsopts -fno-ghci-history -c tc012.hs -fno-warn-incomplete-patterns >tc012.comp.stderr 2>&1 sh: line 0: cd: .typecheckshould_compile: No such file or directory Compile failed (status 256) errors were: *** unexpected failure for tc012(normal) Presumably this is some kind of Windows escape-character problem. But it has worked fine for years, so what is going on? It's very tiresome dealing with Windows breakage so frequently. A few regression test failures, maybe, but outright breakage is very bad. Simon ___ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs
