|
Post closed tickets in your report. | Note: This channel is for our weekly status meetings (Tuesdays at 19:30 UTC); you probably want #parrot instead. | irclog: irclog.perlgeek.de/ Set by moderator on 10 April 2012. |
|||
|
07:50
contingencyplan joined
08:30
lucian joined
09:29
schm00ster joined
12:53
alvis joined
14:01
jashwanth joined
15:20
crab2313 joined
15:45
jashwanth joined
16:16
contingencyplan joined
18:08
lucian joined
19:01
tadzik joined
|
|||
| Coke | Will not be able to make #ps today, probably: covered coke/rm_pasm on parrot-dev mailing list. feedback, more PASM removal commits welcome. | 19:03 | |
| EOR. | |||
|
19:03
whiteknight joined
19:04
benabik joined
19:07
NotFound joined
|
|||
| alvis | What I did: | 19:09 | |
| * NOTE: Primarily, the same report as last week, except | |||
| - Almost complete with 'ayardley/READMEs' - a local branch to update Parrot's 'README' files to 'README.pod' files and to add 'README.pod' files to the top-level directories. | |||
| EOR | 19:10 | ||
| benabik | DID: | 19:11 | |
| * More work on pct_winxed | |||
| * submitted many issues to Winxed (sorry NotFound) | |||
| * Put together a gist on the possible PACT assembly language: gist.github.com/2599989 | |||
| WILL DO: | |||
| * Probably not much, maybe a bit more in pct_winxed | |||
| BLOCKERS: | |||
| * Want to try to pile through as much of my thesis as possible in the next couple weeks before GSoC starts | |||
| EOR | |||
|
19:12
dukeleto joined
|
|||
| moritz | DID: some rm_pasm work. Lots of Rakudo hacking. EOR | 19:12 | |
| dukeleto bought a house and is getting married on Saturday. Just about nothing parrot-related was accomplished. | |||
| moritz | dukeleto++ # double congrtulations | 19:13 | |
| dukeleto | moritz: thanks! It has been a lessen in organized chaos :) | 19:15 | |
| whiteknight | WHAT I DID: | 19:16 | |
| * Digging through the issue tracker. We have almost 500 open tickets, we need to get that number much lower. I'm fixing/closing them as I go. We have over 100 branches, many of those are old and may be deletable. | |||
| * Started a new branch to remove VTABLE_can (but not the "can" op). Going surprisingly smoothly. May be ready to merge shortly after 4.4.0, with testing. | |||
| * Started a branch to remove singleton PMCs. This branch is not going smoothly and, because of the pointer-based interface for singletons, is segfaulty. | |||
| * Fixed pbc_merge to properly deduplicate strings, merge annotation segments, and properly merge debug segments. | |||
| * Fixed pbc_disassemble to do something reasonable when passed no arguments. | |||
| * Fixed LexPad.get_iter to do the correct thing instead of returning the iterator for the corresponding LexInfo. | |||
| * Fixed parrot_debugger to not segfault or do other stupid things when we pass in something that isn't a .pbc. Now, it expects all input files to be .pbc files. | |||
| * Several cleanups to Key PMC and src/key.c, add some introspection methods to Key PMC for working with register-reference keys. | |||
| * Started a branch to enable GC finalization globally. Testing seems to be going well so far, but I don't think anybody has built/tested Rakudo with it yet. | |||
| * Helped rurban++ fix several memory corruption errors he was finding using the clang AddressSanatizer tool. I'm not able to run AddressSanatizer myself because of various config-related issues I'm having | |||
| * Rosella.Net is now tested and considered stable. | |||
| * A large assortment of other small cleanups and fixes as I dig through the ticket queue. | |||
| * Following along with Coke++'s efforts to remove PASM. I have a patch to rip PASM out of the IMCC interface routines and rip out the PASM compreg PMC. This opens the door to detect and remove much pasm-related IMCC code in the future. | |||
| WHAT I WILL DO: | |||
| * 4.4 release is next week. I'm going to fix/cleanup/merge anything that I can do before then. Probably have a freeze on master starting on Sunday. | |||
| EOR | |||
| alvis | dukeleto++ # My congratulations as well! | 19:19 | |
| NotFound | What I did: fixed some of the winxed issues reported by benabik and added some new features. EOR | 19:21 | |
| cotto | did: | 19:22 | |
| * resumed hacking on M0 (made a big todo list, implemented register name aliases, chatting with jimmyz++ and nbrown++ about other things) | |||
| * started working with benabik++ on his pact assembly language, reviewed pct_winxed awesomeness | |||
| * flipped the crazy bit, gave my 2 weeks notice at $dayjob, will start working at a tiny startup on the 22nd. | |||
| will do: | 19:23 | ||
| * continue working through the m0 todo list (gist.github.com/2581153 - comments/forks welcome!) | |||
| * gsoc stuff with benabik | |||
| * -Ofun | |||
| EOR | |||
| dukeleto | cotto++ # congrats on the crazy bit! | 19:24 | |
| cotto | It's that time again. | 19:30 | |
| alvis | hello | ||
| NotFound | Hola | ||
| benabik | o/ | 19:31 | |
| dukeleto waves temporarily | 19:32 | ||
| cotto | How's this week been? | ||
| whiteknight | good | 19:33 | |
| very good | |||
| cotto | indeed | ||
| It's great to see development pick up. | 19:34 | ||
| whiteknight | We've got way too many open tickets in the queue. We need to start focusing on that again | 19:35 | |
| I think we can get down to 450 open tickets by the end of the month without too much stress | |||
| cotto | jimmy++ was also looking through old branches. If he asks about anything, we should make sure to give him a hand. | ||
| whiteknight | yes | ||
| We also have over 100 branches, so if we can prune the tree a little that would be great | |||
| cotto | A issue bash sounds great. | 19:36 | |
| whiteknight | We've got a week until 4.4, and if we can trim some fat in preparation that would be great | ||
| NotFound | I think we are having again "wish list" issues | ||
| cotto | Should we focus on issues, branches or both? | ||
| whiteknight | issues | ||
| cotto | NotFound: can you elaborate? | ||
| benabik | I poured through issues a while back... gave up when #185 led to #346 led to "how do I test this"? | 19:37 | |
| whiteknight | As I found in the last few days, we have several issues which are easily closable. Either they're already fixed but nobody updated the ticket, or the ticket is WONTFIX, or the ticket is a vague wishlist item, etc | ||
| cotto | Consistently closing even a single issue per person-week is meaningful progress. | 19:38 | |
| whiteknight | yes it is | ||
| A lot of old tickets we need to be able to say " I mean no disrespect, but we're not going to keep this open" | |||
| NotFound | cotto: for example, "consider some extern lib for hashing"... I thought the idea was to put that kind of things in wiki pages, not in issues. | ||
| whiteknight | yes. | ||
| dukeleto | +1 to cleansing issues | 19:39 | |
| cotto | NotFound: that can go away or go to the wiki. It doesn't really need an issue and should be very easy to implement for a mildly motivated hacker. | ||
| dukeleto | respectfully close old issues that are ambiguous/wishy | 19:40 | |
| cotto | +1 | ||
| dukeleto | as long as we ask people to create a new, specific issue with updated data, I think it is fine | ||
| benabik | +1 to saving useful information in wiki | ||
| dukeleto | Keeping open issues which are impossible to close is a fools errand. Nobody wins. | ||
| benabik: yes. And closed issues are, of course, still there for public archaeology/etc | 19:41 | ||
| benabik | dukeleto: The information isn't lost, but its discoverability is. | ||
| dukeleto | Having a graph of the current number of issues + branches will help us visualize progress. | ||
| benabik: maybe. Closed issues are just as easy to search as open issues, imho | |||
| benabik | dukeleto: As an open issue it's "hey, I could work on this." Nobody cruses closed issues for things to do. Just throwing my support behind putting those thing in the wiki. | 19:43 | |
| alvis | While we're on issues: I promised I'd bring up kid51's email about "7 .pmc files with undocumented functions ..." to parrot-dev; so, here it is. He would like to know how we should proceed, as well. | 19:44 | |
| cotto | alvis: thanks | 19:45 | |
| I'll take object.pmc | 19:46 | ||
| also needed: namespace, eval, complex, callcontext, bigint, capture | 19:47 | ||
| alvis | So, folks should pick one and work on it, then? If so, I'll take bigint. | ||
| whiteknight | open a ticket, assign it to me. Will be done tonight | 19:48 | |
| cotto | That's what I failed to explicitly suggest, yes | ||
| alvis | cotto: ok, I'll follow up on parrot-dev with the approach. | ||
| whiteknight: ok. how about eval? | |||
| whiteknight | quick warning: most of the comments in eval pmc will be along the lines of BLAH BLAH BLAH THIS PMC IS TEH STOOPID | ||
| cotto | alvis: ok. I'll open an issue | ||
| whiteknight | alvis: that's fine | 19:49 | |
| cotto | whiteknight: those are the best kind | ||
| alvis | cotto: ok. I'll leave it to you to open the issue. | ||
| cotto | github.com/parrot/parrot/issues/768 | 19:52 | |
|
19:53
lucian joined
|
|||
| cotto | and firefox crashed just after submitting the issue | 19:53 | |
| any other questions? | 19:55 | ||
| alvis | that's it from me. | 19:56 | |
| cotto | anyone mind if I make that test fail? Right now it just TODOs underdocumented PMCs | 19:57 | |
| whiteknight | go for it | 19:58 | |
| cotto | and done | 19:59 | |
| alvis | we wrapped? | 20:05 | |
| cotto | I think so. | ||
|
20:05
alvis left
20:06
moritz left,
crab2313 left
20:23
NotFound left
20:26
tadzik left
21:16
benabik left
22:14
whiteknight joined
22:22
lucian joined
23:22
contingencyplan joined
|
|||