Should be enough to get you started with actual development. Once you're past building the software, the developer documentation Version number (because editions don't exist anymore), for example For example, release 6.6.0 of dupeGuru ME is When implementing a big feature, it's possible that it gets its ownīranch until it's stable enough to merge into master.Įvery release is tagged, the tag name containing the edition (for old
Needed, we create maintenance branches for bugfixes of the current Represents what going to be included in the next feature release. Master is the main development branch, and thus The README.md file at the root of this project. At all times, you should be able to build from source aįresh checkout of the master branch using instructions from
You can contribute than taking the chance of missing thatĭupeGuru's source code is on Github and thus managed in a Git Much prefer to spend the time figuring out with you whether (and how) You're having prevent you from going forward, please contact me. If there's any situation where you'd wish to contribute but some doubt Get you started, but if it isn't, then please, open a Normally, this documentation should be enough to So, whatever your skills, if you're interested in contributing toĭupeGuru, please do so. I'm more serious about my commitment to create a community around this
Since the end of 2013, I've been putting a lot of efforts into
Me working on dupeGuru, I've failed at attracting them. Open source for a while now and, although I've ("I" being Virgilĭupras, author of the software) always wanted to have people other than See also the last Fossies "Diffs" side-by-side code changes report for "contribute.rst": 4.2.0_vs_4.2.1.ĭupeGuru was started as shareware (thus proprietary) so it doesn't As a special service "Fossies" has tried to format the requested source page into HTML format (assuming markdown format).Īlternatively you can here view or download the uninterpreted source code file.Ī member file download can also be achieved by clicking within a package contents listing on the according byte size field.
0 kommentar(er)
