Req #51410 [Opn]: Automatic weekly release of 'pman'
| From: | sobak@php.net | Date: | Wed, 14 Dec 2016 20:51:13 +0000 |
| Subject: | Req #51410 [Opn]: Automatic weekly release of 'pman' | ||
| References: | 1 | Groups: | php.doc.bugs |
| Request: | Send a blank email to doc-bugs+get-14234@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=51410&edit=1
ID: 51410
Updated by: sobak@php.net
Reported by: bjori@php.net
Summary: Automatic weekly release of 'pman'
Status: Open
Type: Feature/Change Request
Package: Doc Build problem
Operating System: *
PHP Version: Irrelevant
Block user comment: N
Private report: N
New Comment:
Could we revise it?
> Because then we loose the history if the server crashes, and even the current
> release...
And yet we can regenerate it, we have all necessary sources versioned. I don't think it makes
sense to store compilation results there as well. By the side effect web/doc.git repo is already
heavy as f**k...
Previous Comments:
------------------------------------------------------------------------
[2013-01-17 08:19:13] philip@php.net
We require someone braver than I to solve this problem.
------------------------------------------------------------------------
[2011-07-02 00:56:24] philip@php.net
Currently a human has been building these roughly once per month.
I'll attempt to add this, so assigning to self. Should be fun :)
------------------------------------------------------------------------
[2010-04-28 21:13:47] bjori@php.net
Because then we loose the history if the server crashes, and even the current
release...
------------------------------------------------------------------------
[2010-04-28 21:05:17] philip@php.net
Why not just have the server generate/host them, and skip the svn storage step?
------------------------------------------------------------------------
[2010-03-27 00:06:33] bjori@php.net
Description:
------------
We need to update the PHP Unix manual pages more often.
Currently the online documentation is updated every Friday, and we should
probably to the same for the Unix manual pages.
It shouldn't be hard to script "simplechannelserver.php" (or whatever that was
called) to automatically commit and push new releases to our PEAR server.
One thing to consider; we need to commit the XML files to the docweb repository
so they get updated.
Maybe we should create an "fake phpdoc" SVN account to do the job?
Doesn't quite make sense to mark all those commits by a human - which didn't
actually do crap...
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=51410&edit=1