-
Notifications
You must be signed in to change notification settings - Fork 0
Home
This is a fork of the official FrontAccounting repository. This repository is setup to:
- Support the popular FrontAccounting docker image genebarker/frontaccounting;
(currently defaults to 2.4.3 official) - Serve as the home of my on-the-ground bug fixes, enhancements, and modifications done for clients; and
- Comply with GNU General Public License.
Official releases are tagged so that they can easily be selected.
-
2.4.6 on 24 Dec 2018 commit
4ab13d80235f92856a8b5ed74ba3e07df70aa78f
-
2.4.5 on 07 Dec 2018 commit
080086d679db208567059b420ebfb5fcd7aae5b5
-
2.4.4 on 18 Mar 2018 commit
de943e150d36f815a02d4996e532a5e4e7510bc8
-
2.4.3 on 10 Nov 2017 commit
0f9f517f184a6cae12d1b57b4b6da9cb51efb76b
-
2.4.2 on 31 Jul 2017 commit
480e5f57b0cd2f439b0f8f8ea7cfe9f630b8b4e9
-
2.4.1 on 23 May 2017 commit
615175f06d54958e4074216a1a38fc4302435b85
-
2.4.RC1 on 23 Feb 2016 commit
b235c15fce03f3b6a6eb7187e7c73ad0f3ef33d9
-
2.3.26 on 23 May 2017 commit
113a0f4ffc2b8860505bcc26574e8b6e1dddab65
-
2.3.25 on 21 Feb 2016 commit
00176a65f0735173916fe047f3ea3099474ddc14
-
2.3.24 on 03 Feb 2016 commit
4507cd0059703d39f3e31230c9abe7494334ef4f
For example, say you want to work the hardened 2.3 release:
$ git checkout -b mymod 2.3.26
Switched to a new branch 'mymod'
future stuff I need
+------>------->------+
| |
| v
unstable --> master --> fixes --> sifa
^ ^ |
| | |
+------<-------<------+
stuff FA team wants
- unstable - Official repository's development code
- master - Official repository's production code (releases are tagged)
- fixes - My on-the-ground bug fixes and enhancements
- sifa - Client specific modifications
The workflow is designed to:
- Use the official FrontAccounting repository as the baseline;
- Provide clean way to share my on-the-ground bug fixes and enhancements; and
- To separate out customer specific modifications.
My goal is to keep the fixes branch very close to the official master (with minimal code differences). The strategy for achieving this is to flow ideas back to the official team so that the improvements can make their way into an official release (and out of fixes!).
Currently, the fixes and sifa branches are based on the 2.3 version. The plan is to migrate up to 2.4 after the development activity settles down a bit. Forking from 2.3 long term is not viable.
To see what's in the fixes
branch see the following resources:
- Commit history contains the complete picture
-
FIXLOG.txt
serves as an addendum toCHANGELOG.txt
of official 2.3.25
To see what's in the sifa
branch see the following resources:
- Commit history contains the complete picture
-
SIFALOG.txt
serves as an addendum toCHANGELOG.txt
of official 2.3.25