On the weekend of 27-29/6 we plan to resolve the remaining issues with 7.8. Some of us will meet in person, some will communicate over KOM.
You are encourage to participate virtually even if your preferred medium of communication is IRC or other IM-systems.
great!
could you post something on the newssection of the pike website? i'll be standing by on irc (and maybe install a better kom client for the occasion :-)
greetings, martin.
That would involve remembering my password and how to do it, so no, not right now. Feel free though. :)
fair enough :-) i just checked, and i remember. could you help me with the text though?
like a few more details on what you planto achive? get all solved? shall i post the remaining blockers?
do you have some more pointers on where people can help (other than testing?)
how many people (who) will be at the weekend on location?
anything that's worth mentioning. keywords would be ok.
greetings, martin.
fair enough :-) i just checked, and i remember. could you help me with the text though?
like a few more details on what you planto achive? get all solved? shall i post the remaining blockers?
What jhs said. The blockers on the list should all be solved.
do you have some more pointers on where people can help (other than testing?)
Testing and grabbing blockers. I think the following are easiest to do something about:
[/] Fallback to poll from epoll (from the conference road map). Implemented, but further testing is needed, as well as updated documentation.
Already implemented, but as it says, needs testing, testing, testing.
[ ] mast/zino New Windows build environment.
This is for the normal Unix/Windows/VC8 hybrid. As always, this will probably be the last one to be solved. But we know that Pike can be built in cygwin now, so if someone wants to get that up and running and write a description of how it's done it would acctually be enough for a release in a pinch.
[ ] zino/mast Building external modules should work.
If someone wants to look at this before the weekend it's not massively complicated, just a lot of mechanical checking through the scripts and then testing to see why variables aren't propagated as they should.
[ ] An API for safely creating temporary files. Possibly wrapping mkstemp/mkdtemp.
This is a non-blocker, but would be nice. Fairly trivial to make prototypes of if someone wants to pitch in.
how many people (who) will be at the weekend on location?
Around six or seven I would think. A couple more virtual in Sweden.
anything that's worth mentioning. keywords would be ok.
Fame? Glory? Profit?
On Wed, Jun 18, 2008 at 09:55:03AM +0000, Peter Bortas @ Pike developers forum wrote:
What jhs said.
uhm, could you please have a look at the lyskom bridge? half the messages seem to be dropped. eg on this topic only your two replies came through, nothing else.
greetings, martin.
I did a postfix flush now and hopefully this missing text will come through:
The 7.8 blockers (thread title, also listing non-blockers) thread has been circulating here for some weeks already, last one being 16581076. (16583752) /Johan Sundström (Achtung Liebe!)/
Please let me know if you get the mails. It seems like sometimes they get lost :(
nothing came through yet,
greetings, martin.
I have no clue. It might be your mail-system. Never heard any other complains at the moment and this export seems to work.
the missing messages are not in the list archive at http://lists.lysator.liu.se/pipermail/pike-devel/2008-June/date.html either, so the problem must be between lyskom and lysators listserver.
greetings, martin.
I've solved it! I added some debug-output that mysteriously solved the crashing of the exporter, but now I've figured out why it got "solved":
write("From: ("+utf8_to_string(from)+") "); //Saves Pike from crashing?!? //Yes, because it crashes this Pike-program when getting ISO-ö obviously!
Since Sat May 17 18:51:11 CEST 2008 Neither Henrik Grubbströms nor Johan Sundström's messages have gotten into the archive. It's obviously because the "ö" in their usernames.
Now it should work though, if the 7.6.112-Pike doesn't have the _mystring[3]='f' => crashes Pike sometimes bug. If this comes through with my åäö-parenthesis, then it works.
Writing test cases would also be very useful.
Any test cases really, but if you need idea then take a look at the ChangeLog and pick one change. Then check the test suite to see if there is something there that might cover the area mentioned in the log entry. If not invent a test.
Anyone is more than welcome to improve the changelog. At this moment my work is just getting keywords into the file (almost done with the /lib section. need to recurse the /src path as well).
pike-devel@lists.lysator.liu.se
-
Hedda (Lite ���) ＠ Pike (-) developers forum -
Hedda (www.linkmeet.com/_Chernobyl2008) ＠ Pike (-) developers forum
-
Johan Sundstr�m (Achtung Liebe!) ＠ Pike (-) developers forum
-
Martin Baehr -
Martin Bähr
-
Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum
-
Peter Bortas ＠ Pike developers forum