Where does the content of release report come from?

[Joel Sherrill]

On Wed, May 23, 2018, 10:46 PM Chris Johns <chrisj at rtems.org> wrote:

> On 24/5/18 3:31 pm, Danxue Huang wrote:
> > Hi Dr. Joel and Chris,
> >
> > How is this pdf file generated (see attacked link please)? Is it
> generated by
> > Trac automatically? Or should I generate it manually?
> >
> >
> https://ftp.rtems.org/pub/rtems/releases/4.11/4.11.2/rtems-4.11.2-release-notes.pdf
> >
>
> The release script I gave you invokes the command 'wkhtmltopdf'. This
> command
> takes as an argument the Trac webpage, for example:
>
>  https://devel.rtems.org/wiki/Release/4.11/4.11.2
>
> The command 'wkhtmltopdf' is like a browser but it creates a PDF as output
> rather than to a screen. The release scripts creates a coverpage and joins
> the
> PDF from the Trac Release page to create the release notes.
>
> Please note, the way the release notes are currently done is not what this
> GSoC
> is about. The task for this GSoC is to write Python code to extract the
> needed
> information from Trac's RSS feed. I will send you some details off list
> and we
> can discuss this some more next week in our meeting, which I am looking
> forward too.
>

I suggested looking at the current release notes only as a guide as to what
generally should be in them. Agreed this is a fetch RSS and write something
better.

I suggested in irc yesterday that having an outline to show the intended
goal would be nice. Perhaps even a mock up of the result with limited
content.

Personally, I find writing without an outline hard so that may be my style
showing.


> Chris
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20180524/385edd77/attachment-0002.html>