# Restructuring NEWS? - Thread: https://externals.io/message/50375 - Original archive: https://news-web.php.net/php.internals/50375 - Started by johannes@schlueters.de on 2010-11-18T22:39:38+00:00 - Messages: 10 - 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 --- ## #50375 — johannes@schlueters.de — 2010-11-18T22:39:38+00:00 URL: https://externals.io/message/50375#50375 Hi, after the 5.3.3 release I was approached with the request to restructure the NEWS file -- for instance by grouping entries by extension -- so users can identify whether there are bug fixes relevant for them etc. The list itself is rather long. Anybody opinions on this? Anybody who wants to play with it to come up with a nice layout which is compact while still helping these people? Maybe it is enough to do this only online on the release web page? Thanks, johannes --- ## #50376 — Jani Taskinen — 2010-11-19T00:23:53+00:00 URL: https://externals.io/message/50375#50376 · In reply to: #50375 19.11.2010 0:39, Johannes Schlüter kirjoitti: > Hi, > > after the 5.3.3 release I was approached with the request to restructure > the NEWS file -- for instance by grouping entries by extension -- so > users can identify whether there are bug fixes relevant for them etc. Something that I did in trunk NEWS perhaps? I'd like a better formatted NEWS though. And get rid of those ancient Changelog* files as well. :) Ideas / examples of better format accepted, I can always implement it if time permits. It would also help if we can forget that 80 chars per line limit as well. It's 2k already and people do have bigger terminals nowadays. --Jani --- ## #50377 — jerome@loyet.net — 2010-11-19T00:28:04+00:00 URL: https://externals.io/message/50375#50377 · In reply to: #50376 2010/11/19 Jani Taskinen : > 19.11.2010 0:39, Johannes Schlüter kirjoitti: > > […] > > > […] > > Something that I did in trunk NEWS perhaps? I'd like a better formatted NEWS > though. And get rid of those ancient Changelog* files as well. :) > > Ideas / examples of better format accepted, I can always implement it if > time permits. It would also help if we can forget that 80 chars per line > limit as well. It's 2k already and people do have bigger terminals nowadays. +1 on the 80 chars per line limit. I hope no one is still using a "everyday" serial terminal :) > > --Jani --- ## #50378 — Gustavo Lopes — 2010-11-19T00:40:07+00:00 URL: https://externals.io/message/50375#50378 · In reply to: #50377 > 2010/11/19 Jani Taskinen : > > […] > > +1 on the 80 chars per line limit. I hope no one is still using a > "everyday" serial terminal :) > I'm not using a serial terminal, but I usually use a font so big that the window only has 80-110 columns. I'm sure I'm not alone. -- Gustavo Lopes --- ## #50379 — johannes@schlueters.de — 2010-11-19T09:30:26+00:00 URL: https://externals.io/message/50375#50379 · In reply to: #50376 > 19.11.2010 0:39, Johannes Schlüter kirjoitti: > > […] > > Something that I did in trunk NEWS perhaps? I'd like a better formatted > NEWS though. I didn't see that change but yeah something like that. Aybody volunteers to go through the 5.3 NEWS? :-) > And get rid of those ancient Changelog* files as well. :) I proposed this in the past. Some people complained. Nobody fixed it (it is not being updated since the switch to svn, before that only cvs HEAD was updated, no branches...) and I didn't see anybody complaining this tells me nobody really needs them. Using svn history features is more effective anyways ... > Ideas / examples of better format accepted, I can always implement it if > time permits. It would also help if we can forget that 80 chars per line > limit as well. It's 2k already and people do have bigger terminals > nowadays. I like having multiple 80 chars terminals next to each other :-) But I think most editors can wrap or cut it off as one prefers. We should avoid 300 char lines though. johannes --- ## #50381 — johannes@schlueters.de — 2010-11-19T09:38:31+00:00 URL: https://externals.io/message/50375#50381 · In reply to: #50379 > > […] > > I proposed this in the past. See http://www.mail-archive.com/internals@lists.php.net/msg46669.html If nobody creates a process for updating these files I will drop the ChangeLog* files before packaging 5.3.4RC2 in two weeks. The current state is useless. johannes --- ## #50380 — Derick Rethans — 2010-11-19T09:39:44+00:00 URL: https://externals.io/message/50375#50380 · In reply to: #50376 > It would also help if we can forget that 80 chars per line limit as > well. It's 2k already and people do have bigger terminals nowadays. No please, don't change that. Even though some screens are larger, the defacto screen size when you login somewhere is 80x24. I hardly change the size, but instead have 4 open that show at the same time. regards, Derick -- http://derickrethans.nl | http://xdebug.org Like Xdebug? Consider a donation: http://xdebug.org/donate.php twitter: @derickr and @xdebug --- ## #50382 — Jani Taskinen — 2010-11-19T09:51:51+00:00 URL: https://externals.io/message/50375#50382 · In reply to: #50381 > > > […] > > See http://www.mail-archive.com/internals@lists.php.net/msg46669.html > > If nobody creates a process for updating these files I will drop the > ChangeLog* files before packaging 5.3.4RC2 in two weeks. The current > state is useless. Do it also in trunk.. :) --Jani --- ## #50396 — Felipe Pena — 2010-11-19T21:48:25+00:00 URL: https://externals.io/message/50375#50396 · In reply to: #50379 Hi, 2010/11/19 Johannes Schlüter > > > […] > restructure > > […] > > I didn't see that change but yeah something like that. Aybody volunteers > to go through the 5.3 NEWS? :-) > > I groupped the the 5.3.4RC1 entries: http://dpaste.com/277482/plain/ Is it okay to commit? :) -- Regards, Felipe Pena --- ## #50402 — Simas Toleikis — 2010-11-20T09:50:21+00:00 URL: https://externals.io/message/50375#50402 · In reply to: #50396 > I groupped the the 5.3.4RC1 entries: http://dpaste.com/277482/plain/ > > Is it okay to commit? :) > > Wouldn't it be better to group PHP-FPM changes in a single block rather than two separate for additions and fixes? /Simas