handbook update for master branch

[Jack]

On 8/2/23 01:44, thb at net-bembel.de wrote:
> Jack via KMyMoney-devel schrieb am 01.08.2023 22:06 (GMT +02:00):
>> I'd like to start updating the manual/handbook for the eventual 6.2.
>> I'd like to start now, with the hope of having it all or at least mostly
>> done by the time we do eventually release 6.2, unlike the still
>> incomplete migration from KMM4 to KMM5.
> Make sure that the version will be 5.2 (working title). My current plan
> is to change the version to be more release date based, so something like
> 23.08 for August 2023. But for now, I used 5.2 on the bugtracker also
> and we should stick with it, at least internally. 6.x can be used when
> we move to Qt6.
Sorry, that was sloppy typing.  I definitely meant 5.2.
>
>> I'd also like to find a way that the process can be collaborative, but I
>> don't want to clutter master branch with gobs of small commits, and I
>> don't want to make extra work for translators when there is likely to be
>> repeated edits to the same sections.  Would it be reasonable to create a
>> Handbook-6.2 branch for this?  I can imagine there being MRs against
>> this branch. This could be merged back into master when at least one or
>> two chapters are complete.
>>
>> Thoughts and suggestions?
> Yes, that makes sense. Calling it Handbook-5.2 does not interfere with the
> translation team which is working from master and stable (5.1).
>
> In case you plan to work on multiple chapters in parallel (multiple persons),
> you might want to create a branch off of the Handbook-5.2 branch for each
> such chapter. That way, you can merge them seperately into the main Handbook
> branch and sync that with the master branch now and then to keep changes
> for the translation teams at a controllable minimum.

Thanks.  Also a good idea.


Jack