Re: [office] Checks on the ODF 1.3 specification in HTML

[Patrick Durusau <patrick@durusau.net>]

Thorsten,

On the pipelining, yes and no.

Pipeling is a great idea, but not for the official releases.

I say that because the official releases are given to the TC Admin that
then preps the files for the "official" location.

Having said that and without asking, I suspect a pipeline that produces
non-official releases would be like other TC artifacts. That "official"
releases with the same content exists shouldn't trouble anyone.

Thoughts?

Hope you are having a great week!

Patrick

On 2/5/20 11:24 AM, Thorsten Behrens wrote:
> Hi Svante,
>
> Svante Schubert wrote:
>> I did some tests on the ODF 1.3 HTML specification and would like to share
>> my notes:
>>
> Thanks a lot!
>
>> [lots of checks]
>>
> and
>
>> I suggest we should fix the naming for the next release and use the prior
>> naming convention of ODF 1.2.
>>
> Agree to pretty much all points.
>
> I suspect the best way to streamline this is to automate as many steps
> as possible, and treat future ODF releases more like a software
> artifact (with a build pipeline & automated test runs)?
>
> Perhaps with the OASIS Open Projects initiative, there would even be a
> repository were we could stick this release automation into?
>
> Best regards,
>
> -- Thorsten

-- 
Patrick Durusau
patrick@durusau.net
Technical Advisory Board, OASIS (TAB)
Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)

Another Word For It (blog): http://tm.durusau.net
Homepage: http://www.durusau.net
Twitter: patrickDurusau

Attachment: signature.asc
Description: OpenPGP digital signature