Thank you very much for the respond. As this isn’t a pressing matter I will simply wait for the texlive2018 update
and get the newest version of l3build.

Ben


> Am 20.04.2018 um 15:31 schrieb Joseph Wright <[log in to unmask]>:
> 
> On 20/04/2018 14:24, Benedikt Vitecek wrote:
>> Greetings,
>> I am using l3build lately and noticed that the date printed in the document title (if \date is not used) using e.g.
>>   	texlua build.lua doc
>> for compilation is wrong. Instead of the current date (which would today be „April 20, 2018“) I get „May 20, 2016“.
>> Interestingly, if I compile the .dtx file directly (using e.g. pdflatex) I get the correct date.
>> I don’t know if I do something wrong … but here are the documents I use:
>> My reduced test .dtx file:
>> 	% \iffalse
>> 	%<*driver>
>> 	\documentclass{l3doc}
>> 	
>> 	\begin{document}
>> 	\DocInput{\jobname.dtx}
>> 	\end{document}
>> 	%</driver>
>> 	% \fi
>> 	% \GetFileInfo{\jobname.sty}
>> 	% \title{The \pkg{\jobname} package}
>> 	% \maketitle
>> 	%
>> 	% \begin{documentation}
>> 	% \end{documentation}
>> 	%
>> 	% \begin{implementation}
>> 	%    \begin{macrocode}
>> 	\def\Versuch{Versuch}
>> 	%    \end{macrocode}
>> 	%\end{implementation}
>> The .ins file:
>> 	\input l3docstrip.tex
>> 	\askforoverwritefalse
>> 	\generate{\file{\jobname.sty}{\from{\jobname.dtx}{package}}}
>> 	\endbatchfile
>> And the build.lua file:
>> 	#!/usr/bin/env texlua
>> 	
>> 	module = "test"
>> 	
>> 	kpse.set_program_name("kpsewhich")
>> 	dofile(kpse.lookup("l3build.lua“))
>> I am currently using the 2018/02/20 version of l3build and texlive2017. Do I need to specify the printed date somewhere?
>> Ben
> 
> Hello Ben,
> 
> This was due to an oversight on my part: I'd set the epoch for both testing and documentation building in the script, expecting that doc dates would always be explicit in sources. The 2018-03-08 release fixes this, but you can add
> 
>    forcedocepoch = false
> 
> to your build.lua file to sort the problem for the moment.
> 
> Joseph