Difference between revisions of "KDE Games/Git Conversion Progress"
|Line 49:||Line 49:|
Revision as of 15:28, 20 April 2012
This page is used to keep track of progress in KDEGames's conversion from SVN to Git.
How to Fill Out the Table
The progress table uses a Mediawiki template with named parameters, to make it easier to edit than the raw table markup.
- When you start writing rules for a particular game, add your initials in a rulesby= parameter, and set inprogress=1; for example rulesby=NA|inprogress=1. This will indicate that the rules are in progress so that efforts aren't duplicated.
- Once you've written the rules and feel they're complete, push them to the kdegames directory of the kde-ruleset repository and remove inprogress=1 from the table. The "Rules" column will automatically turn into a link pointing to the rules file.
- Once you've generated a repository from the rules and verified its correctness, push it some place public, preferably a personal scratch repo. Add a scratch= param with the scratch repository path, and a scratchby= param with your initials; for example scratch=scratch/nalvarez/kdegames-foo.git|scratchby=NA.
- Checkout the repository, poke around a bit and then perform each of the following checks, adding your initials in each column. Ideally, more than one person should check each repo, in which case, separate each set of initials with a comma.
- Main history
- The complete history is present. The first commit should be the initial import into KDE's CVS or SVN. All transitions from playground, kdereview, extragear, KDE3, etc. should be present. Example
- The user documentation is in a subdirectory named "doc". The history of the doc folder should match that of the "kdegames/doc/<game>" folder. In very early revisions there can be a doc/ or html/ folder inside the game.
- The repository has only one head. (git branch -r) Two heads mean a broken master branch. (if that shows more than one commit, something is wrong)
git log --format='%h %p' --all | grep '^[0-9a-f]\+ *$'
- Stable branches
- All relevant stable branches are present. If a game entered the kdegames module for the 4.3 release, it should have a stable branch "KDE/4.x" for each x >= 3 and none for x < 3.
- All relevant release tags are present. If a game entered the kdegames module for the 4.3 release, it should have tags "v4.x.y" and newer.
- If the game has a non-linear history (i.e. work branches were created and later merged back in to trunk) that should be recreated in the Git history. This is by far the most difficult check. Use "gitk --all" or "qgit --all" to visualise branches and merges, but you have to know what you're looking for. Fortunately, this isn't required for games that have a simple playground -> kdereview -> kdegames history. To determine where an application has been throughout its history, enter its name into this page, which will return all known SVN change paths containing the name. (Pay no attention to the l10n and www stuff.)
|Rules||Repo||Main history||Docs||Heads||Stable branches||Tags||Branches|
|KShisen||FS||early tags broken|
- out-of-kdegames tags: http://websvn.kde.org/tags/kgoldrunner/
- Christian Krippendorf
- Frederik Schwarzer
- Mathias Kraus
- Nicolás Alvarez
- Ni Hui
- Parker Coates
- Stefan Majewsky
- Wolfgang Rohdewald
This page was last edited on 20 April 2012, at 15:28. Content is available under Creative Commons License SA 4.0 unless otherwise noted.