User talk:ConradPino/Christian Wimmer/JwaWintrust.pas Incomplete

Committing Work In Progress

My preferred working process is always backed by a Source Code Repository. I establish one or more "work in progress" or "unstable" branches; a distinct branch for each distinct task (deliverable work units). Upon completing a task the branch is merged into the trunk, conflicts resolved and only then committed on the trunk. I shall follow this process; the only question is on which repository.

I propose establishing an "unstable" branch parallel to "trunk" on SourceForge Subversion for use by project developers to commit incomplete works in progress. If this is agreeable we should discuss usage conventions with the "unstable" branch. Conrad T. Pino 17:06, 30 January 2010 (UTC)

ChristianWimmer 17:25, 30 January 2010 (UTC) :

There is no need to create a new branch because the trunk is marked as unstable, inofficial and for testing purposes only. Everbody who uses it must be aware that the build process fails. Usually, only people with some knowledge use this version because they know how to resolve the problem or switch to a working version.

However, we could create a folder in trunk called "unfinished" that contains source translations in progress. All files which are put into the trunk folder are removed from this folder.

For easier access the old JwaWinTrust file can be renamed to e.g. JwaWinTrust_old.pas, so people can still use them if something bad happens.

Conrad T. Pino 17:55, 30 January 2010 (UTC) Agreed, please commit this work unit to "unfinished" branch.

ChristianWimmer 18:17, 30 January 2010 (UTC) I have commited the file into this folder: /jedi-apilib/jwapi/trunk/Win32API/incomplete