Updating user guides to LibO 3.4.2

Hi :slight_smile:
But the 3.3.x series is still being worked on and new releases are due in it's
series?
Regards from
Tom :slight_smile:

It's only *bugfix* releases, no feature changes.

Therefore, such releases are irrelevant for documentation.

*Feature* changes are indicated in the second place (3.X), while
bugfixes happen thereafter in the third place for each code line
independantly (3.3.X or 3.4.X).

Nino

Hi :slight_smile:
Ok, whatever reason the 2 different branches are being developed alongside each
other, both are available to users and so both need documentation.

Early 3.3.x series releases claimed to have longer term support for about a year
so we need to keep documentation available for a year for that series.
Presumably that will occasionally need updating as bug-fixes might sort certain
things out or tweak things a bit.

Regards from
Tom :slight_smile:

... or we find mistakes in the docs themselves. But those changes will
be fairly trivial to make, in terms of effort.

Nino, thanks for your explanation. With your help, I think I'm getting
it figured out now. I've been reading the "new features and fixes" page
for v3.4.x and that has helped too.

--Jean

Hi,

David would know, but I don't think that would work. At the moment you
need a login to get to files on Alfresco, so I would think a link from
the wiki would fail.

media.libreoffice.org is well underway and should be ready "soon" but,
at the present time, Jean is correct.

Also, the location of files on Alfresco occasionally changes, so the
links could get mucked up.

Yes, the Alfresco platform is still very a work in progress, so maybe
we'd decide to change a few things.

At this time we are not storing the PDFs on Alfresco, but that could
change.

My 2 cents is that it would be a good idea to put the PDF files on
Alfresco, too.

There is some merit in not keeping two copies of the published chapters
(one on Alfresco and one on the wiki), so your suggestion could be
useful if it's technically feasible.

I'd say it's an idea that could be discussed again in the near future,
once we can reasonably say that development work on workflows for
alfresco.libreoffice.org, and on media.libreoffice.org as a public
front end for Alfresco, has reached 1.0-type completion. For the
moment, IMHO, it makes better sense to keep things as they are and use
the wiki as the final drop point.

I think David has agreed to include some meta info in the filename, so
the "different names on the wiki" issue is taken care of... and those of
us who want that info for other reasons are, I hope, happy too.

After talking with Jean, what I suggested was to keep some minimal
differentiation in the file names and to place a lot more information
in the document's meta info, including such stuff as subject tags,
author info maybe, and other content. But I'll write back to the list
with detailed proposals, so as to get agreement from the team before
actually changing anything.