Where to find this code

Thomas Baumgart thb at net-bembel.de
Sun Dec 29 08:31:03 GMT 2019


Hi,

please find my answers inline.

On Samstag, 28. Dezember 2019 23:48:03 CET jvapr27 at gmail.com wrote:

> Thanks Thomas. 
> I am trying to read between the lines. So if I miss something, please
> let me know. 
> Here is what I did: 
> 	git clone --single-branch --branch master
> git://anongit.kde.org/kmymoney.git kmy/master	git clone --single-
> branch --branch 5.0 git://anongit.kde.org/kmymoney.git kmy/stable
> Is that what you meant by master and stable? Why do you all see 5.0 as
> stable? Is that the base release that all current security and other
> patches are going towards for the current release, and Master is the
> new source for the next release? (so you apply the patches to both)

Hope the following does not confuse you more. In general we have two states
of the application which we call unstable and stable. Unstable is the current
top development and may have cause or causes trouble with your data file (though
we did not have that in a long time). New features are added to the unstable
branch.

The stable branch is where we only add bug fixes or small improvements but
nothing big that may break the application.

Since we use git as the version control system we use two branches to reflect
the above: master contains the unstable version. Whenever we decide to create
a new stable version off of master (with all the features and such) we create
a new branch and label it with the base version number. This happened the last
time on 2018-02-04 around commit 493a57657a6. This commit also contains the
tag v5.0.0 and is the base of branch 5.0. If you follow the branch you will
come along all those other bug-fix releases and their tags v5.0.1 - v5.0.7.
They all reside on branch 5.0 (the stable branch).

Once we are confident, that we can create a new version off of master, we
have to decide how to call it and then create a new branch with that name
off of master and declare this new as the stable branch. 5.0 will then be
history as the stable branch and does not receive any more fixes. OK,
exceptions may apply.

Then there is the branch Brandon brought into play: 4.8. It is the last stable
branch that is based on KDE4/Qt4 technology. This was created just like the
5.0 branch on 2016-06-14 with commit 25cbb1a0d11f40. After that, master was
turned into the KF5/Qt5 version.


> Regarding Step C... So then, we have to do a(n) (re)installation to
> make sure all the plugins get pulled correctly.. otherwise, I won't see
> the changes. This makes sense, although.. I am wondering, are the
> Reports modules considered a plugin or part of the core of KMyMoney?
> Also, do you happen to know if Kdevelop runs a re-install behind the
> scenes when I hit the Debug button? 

My explanation about the two sandboxes should only describe how I manage
to switch pretty fast between the two versions (unstable/stable) without

recompiling every time. If you don't need to do that, say you are only
working on a fix on the stable branch, then you don't have to set it up
that way.

Currently, the only requirement is, that only a single version is installed.
I know that some folks have played around with environments to have KMyMoney
installed in parallel in different versions, but that is a more complex setup 
and requires a bit of knowledge. This also implies that no package containing
KMyMoney from the distro repository is installed on the system.

In 5.0 some of the core modules have been converted into plugins. So functionality
wise they belong to the core of the application and are build with it but
technically they are plugins (and can be deactivated by the user).

KDevelop can be instructed to run a 'make' or 'make install' before it starts
debugging/executing. This is controlled through the Launch Configuration setting
of Dependencies/Action. I usually have this set to 'Do nothing' and control the
things myself.

> thanks again. I know you have mentioned some of this in the past and
> some of it is just now sinking in. I promise once I get going, I will
> try to help you all instead of just slowing you guys down. I just
> finally have some down time from my regular work that I can focus on
> this.  

Don't worry about that. We are here to help. And believe me: it is how we all
learned to do this.

Thomas


-- 

Regards

Thomas Baumgart

https://www.signal.org/       Signal, the better WhatsApp
-------------------------------------------------------------
Bachelor: One who is footloose & fiance free!
-------------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 868 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kmymoney-devel/attachments/20191229/2f5c7486/attachment.sig>


More information about the KMyMoney-devel mailing list