# win32 snaps back - Thread: https://externals.io/message/38776 - Original archive: https://news-web.php.net/php.internals/38776 - Started by Pierre Joye on 2008-07-05T16:33:16+00:00 - Messages: 8 - Reply by email to internals@lists.php.net - More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt --- ## #38776 — Pierre Joye — 2008-07-05T16:33:16+00:00 URL: https://externals.io/message/38776#38776 Hi, The win32 snaps were broken since the 24th of June. Except the 5.3 apache2filter and the 5.3 installer snapshots, everything is back online. The apache2filter is broken (all platforms) on 5.3 right now and will be fixed soon (Thanks to Scott). By the way, it would be nice if every PECL maintainers begin to fix their extension to work with 5.3 (reference counting macros update). Cheers, -- Pierre http://blog.thepimp.net | http://www.libgd.org --- ## #38783 — johannes@php.net — 2008-07-05T19:34:45+00:00 URL: https://externals.io/message/38776#38783 · In reply to: #38776 Hi, > The win32 snaps were broken since the 24th of June. Except the 5.3 > apache2filter and the 5.3 installer snapshots, everything is back > online. Thanks for that, while working on the Windows stuff: Do you think you can find a good way to send notices to the list or at least me (and Lukas) once the build fails. In past we had enough situations where snaps were broken for a few days without anybody seeing which makes finding the cause harder... When doing that please keep in mind not to spam the list too much so only send a mail out when it fails for the first time, not every two hours when the snaps box tries again. Thanks, johannes --- ## #38784 — Pierre Joye — 2008-07-05T20:00:22+00:00 URL: https://externals.io/message/38776#38784 · In reply to: #38783 hi, > Hi, > > > > […] > > Thanks for that, while working on the Windows stuff: Do you think you > can find a good way to send notices to the list or at least me (and > Lukas) once the build fails. In past we had enough situations where > snaps were broken for a few days without anybody seeing which makes > finding the cause harder... > > When doing that please keep in mind not to spam the list too much so > only send a mail out when it fails for the first time, not every two > hours when the snaps box tries again. Yes, that's in our TODOS. It will be (more easily) possible once we've splitted PECL and php-src builds. The idea is to open bugs for a given extension instead of mailing the list(s). It should be ready in the next two weeks but if one likes to help for the web bug parts, please raise your hand (Bary?) :) Cheers, -- Pierre http://blog.thepimp.net | http://www.libgd.org --- ## #38789 — Pierre Joye — 2008-07-06T11:09:39+00:00 URL: https://externals.io/message/38776#38789 > Hello Pierre, > > Saturday, July 5, 2008, 10:00:22 PM, you wrote: > > > […] > > > […] > > > […] > > Interesting idea. How about an auto assigner to the maintainter as well? > Probably auto cc'ing the peple listed in credits. Hmmm, that would bring > us back to people.php.net and having email adresses in credits files. The > other option I can think of is auto assign by author info in the headers. The new issues tracker will let us define maintainers, developers, helpers, etc. per category/package/extensions. That will be of great helps. In the current state, many extensions are maintained by the active PHP developers and not by the original authors, that's why I would prefer a solution not related to the CREDITS or header info. Until the new issues tracker is in place, we can "manually" maintain this file for this script. How the script could work: * Snaps box - the snaps scripts upload a list of errors per extension (json? :) * bugs.php.net (cron job) - parse the list - Fetch the (active) maintainers list from the "db" - mail the maintainers - create a bug report It is not clear to who it should be assigned, I will talk to Bary to get a "assign to maintainers" function as it is often not a good thing to assign to one person only as we never know if a) he will actually work on it or b) if he has the time to do it. Having more persons informed or assigned will let them decide who will fix the issue and when (in the hope that our legendary team work abilities will work ;-). By the way, we may move this discussion to php-qa :) Cheers, -- Pierre http://blog.thepimp.net | http://www.libgd.org --- ## #38791 — Lukas Kahwe Smith — 2008-07-06T18:29:12+00:00 URL: https://externals.io/message/38776#38791 · In reply to: #38789 > In the current state, many extensions are maintained by the active PHP > developers and not by the original authors, that's why I would prefer > a solution not related to the CREDITS or header info. Until the new > issues tracker is in place, we can "manually" maintain this file for > this script. Good point, but should this information still come with the source? So ideally the bug tracker can pick this information from an "active maintainer" list in the CREDITS? regards, Lukas Kahwe Smith mls@pooteeweet.org --- ## #38792 — Pierre Joye — 2008-07-06T18:49:06+00:00 URL: https://externals.io/message/38776#38792 · In reply to: #38791 > > > > > > […] > > Good point, but should this information still come with the source? So > ideally the bug tracker can pick this information from an "active > maintainer" list in the CREDITS? This information is not in the source, not in CREDITS and not in the headers. Cheers, -- Pierre http://blog.thepimp.net | http://www.libgd.org --- ## #38793 — Lukas Kahwe Smith — 2008-07-06T18:49:35+00:00 URL: https://externals.io/message/38776#38793 · In reply to: #38792 > On Sun, Jul 6, 2008 at 8:29 PM, Lukas Kahwe Smith > wrote: > > […] > > This information is not in the source, not in CREDITS and not in the > headers. Right, my point was that it should be there. regards, Lukas Kahwe Smith mls@pooteeweet.org --- ## #38795 — Pierre Joye — 2008-07-06T19:06:08+00:00 URL: https://externals.io/message/38776#38795 · In reply to: #38793 > > > > > […] > > > Right, my point was that it should be there. Not necessary, nice maintainers are not the authors. But! we have EXTENSIONS :-) http://cvs.php.net/viewvc.cgi/php-src/EXTENSIONS?revision=1.72.2.4.2.5&view=markup Let see what I can do out of it. -- Pierre http://blog.thepimp.net | http://www.libgd.org