Export Kexi documentation from userbase to docbook
Yuri Chornoivan
yurchor at ukr.net
Sun Oct 23 12:51:45 BST 2011
написане Sun, 23 Oct 2011 00:40:59 +0300, Jaroslaw Staniek
<staniek at kde.org>:
> I have one rather general question, do you think updates to the
> documentation have to be synchronized with Calligra/Kexi releases?
> Even if there's change and no release for an app, project members
> would want to extend documentation with bits they planned but just not
> made it for the release for whatever reason.
>
> I think both Calligra developers and members of the Documentation
> Team(s) could express their opinion on this one.
> I particularly would see liberal approach for documentation release
> schedules as nice but also can accept the rule when online
> documentation is ahead of the offline one.
> And I am assuming there is no concept of freezing periods for online
> documentation, but only expectation that it should be always made in
> "stable/clean" state each time the Doc Team grabs the content for
> offline releases.
>
> Would be great to note down see some such rules that we're collecting,
> as "official" - if there is anything missing.
>
Hi,
For me, as a translator it would be good to follow KDE schedules:
1. Documentation export to master 14 days after hard feature freeze.
2. Documentation export to branch right after minor release (there should
be some agreement on not including documentation for new features into
branch releases). master/branch separation can be done by the different
page list (separate pages for new features on UserBase). If separation
cannot be done, then we need some other rules (special tags for versions
or something else).
Best regards,
Yuri
More information about the calligra-devel
mailing list