Policies/Application Lifecycle - Revision history

Drf: /* Stage 2: Stable */ update to git

2011-12-15T14:36:21Z

‎Stage 2: Stable: update to git

Aseigo at 08:10, 19 July 2011

2011-07-19T08:10:06Z

Odysseus: moved Policies/SVN Guidelines to Policies/Application Lifecycle: Rename for git reorg

2011-03-06T17:11:35Z

moved Policies/SVN Guidelines to Policies/Application Lifecycle: Rename for git reorg

Odysseus at 14:05, 1 March 2011

2011-03-01T14:05:38Z

Lueck: /* Translations */

2010-04-02T20:02:14Z

‎Translations

Lueck: /* Stage 3: The end */

2010-03-01T20:10:17Z

‎Stage 3: The end

Chani: /* Stage 2: Stable */ hoping this will reduce common mistakes

2009-08-03T20:24:09Z

‎Stage 2: Stable: hoping this will reduce common mistakes

Steveire: /* Stage 2: Stable */ Add link to Suggested_Review_Criteria page.

2008-10-30T13:30:39Z

‎Stage 2: Stable: Add link to Suggested_Review_Criteria page.

Kleag: Added reminder to move the doc also when moving the application

2008-05-11T17:35:39Z

Added reminder to move the doc also when moving the application

Frinring: link to coordinator overview

2008-03-27T13:27:20Z

link to coordinator overview

@@ Line 34: / Line 34: @@
 * Your application should be [[Development/Tutorials/Localization/i18n|completely translatable]].
-When you decide you want to move to this second stage, use `svn mv` to move your application to {{path|/trunk/kdereview}} and announce the move on '''kde-core-devel@kde.org''' (no, project mailing lists are not good enough). In the announcement address the above issues and state where you want your application to move to (which KDE main module or extragear). Extragear only requires general approval on kde-core-devel. A main module requires approval from the community who manages that module (e.g. the kdepim module requires approval from the kdepim community). Don't forget to move the documentation of your application to {{path|/trunk/kdereview/doc}}. Some suggestions for reviewers to consider when reviewing new applications and library code are on [[Policies/Suggested_Review_Criteria]].
+When you decide you want to move to this second stage, file a sysadmin bug report for your application to be moved to KDE Review, and announce the move on '''kde-core-devel@kde.org''' (no, project mailing lists are not good enough). In the announcement address the above issues and state where you want your application to move to (which KDE main module or extragear). Extragear only requires general approval on kde-core-devel. A main module requires approval from the community who manages that module (e.g. the kdepim module requires approval from the kdepim community). Some suggestions for reviewers to consider when reviewing new applications and library code are on [[Policies/Suggested_Review_Criteria]].
-The move to kdereview starts a two week review period during which the community can object to your proposal or request additional changes. If there are no objections or requested changes after this two week period, you are allowed to move your application to the place you requested. If your intention is to move to a main module you must additionally get approval from the [[Projects/Release_Team#Module_Coordinators|module coordinator(s)]] who manage that module.
+The move to kdereview starts a two week review period during which the community can object to your proposal or request additional changes. If there are no objections or requested changes after this two week period, you are allowed to move your application to the place you requested, filing a sysadmin bug again. If your intention is to move to a main module you must additionally get approval from the [[Projects/Release_Team#Module_Coordinators|module coordinator(s)]] who manage that module.
 If changes are requested, you can leave your application in kdereview while you are actively working on those issues. If you lack the time to work on the changes, move your application back to playground. Once the requested changes are completed, announce to kde-core-devel that you have completed the requested changes and wait for another week for objections.

@@ Line 12: / Line 12: @@
 === Stage 1: The start ===
-The start of a new application can take place on a local disk, in a local repository or any other way. Another option is provided by KDE in the special {{path|/trunk/playground}} folder in the repository where everyone is free to commit ones own application. You can [[Contribute/Get_a_SVN_Account | request an SVN account]] and after that you can import your project in the subfolder of your choice. Applications in playground are organized in folders like KDE is itself. For example, games are in {{path|/trunk/playground/games}}. In each of these folders, there is a {{path|doc}} folder where you should put the docbook documentation of your application.
+The start of a new application can take place on a local disk, in a local repository or any other way. Another option is provided by KDE in the special {{path|/trunk/playground}} folder in the repository where everyone is free to commit ones own application. You can [[Contribute/Get_a_Contributor_Account | request an KDE Contributor account]] and after that you can import your project in the subfolder of your choice. Applications in playground are organized in folders like KDE is itself. For example, games are in {{path|/trunk/playground/games}}. In each of these folders, there is a {{path|doc}} folder where you should put the docbook documentation of your application.
 It is not meant as a backup area, so you should not develop your application somewhere else and only sync the changes now and then to KDE's repository.

← Older revision		Revision as of 14:05, 1 March 2011
Line 1:		Line 1:
		+	{{warning\|This page is yet to be reviewed for changes required by the migration to Git. Information and commands on this page may no longer be valid and should be used with care. Please see the [[Development/Git\|KDE Git hub page]] for more details. }}
		+
	When you want to start a new application (or remove an old application), you want to know where you should place it in the Subversion repository. This document describes where to go in which stage of your application.		When you want to start a new application (or remove an old application), you want to know where you should place it in the Subversion repository. This document describes where to go in which stage of your application.

@@ Line 44: / Line 44: @@
 === Translations ===
-For each move in subversion, the translation files of each language need to move as well. Because this requires a complete checkout of the l10n folder and some knowledge about the structure, you can ask the release-team ('''release-team@kde.org''') to move them. Send a simple mail with the information required to do the move, for example: 'move {{path|/playground/somewhere/someapp}} to {{path|/kdereview/someapp}}'.
+For each move of code and documentation in subversion, the translation files of each language need to move as well. Because this requires a complete checkout of the l10n folder and some knowledge about the structure, you can ask the i18n team ('''kde-i18n-doc@kde.org''') to move them. Send a simple mail with the information required to do the move, for example: 'move {{path|/playground/somewhere/someapp}} to {{path|/kdereview/someapp}}'.
 If you want to help out with these kinds of moves, please send a mail! You are welcome to help out.

@@ Line 41: / Line 41: @@
 === Stage 3: The end ===
-Whenever you decide to stop developing the application and that leaves the application without developers, please announce that to kde-core-devel. If nobody stands up to take over maintainership within two weeks, the application has to be moved to the {{path|/trunk/unmaintained/N/}} area as every application in the KDE main modules and in extragear needs to have a maintainer to stay there.
+Whenever you decide to stop developing the application and that leaves the application without developers, please announce that to kde-core-devel. If nobody stands up to take over maintainership within two weeks, the application has to be moved to the {{path|/tags/unmaintained/N/}} area as every application in the KDE main modules and in extragear needs to have a maintainer to stay there.
 === Translations ===

@@ Line 32: / Line 32: @@
 * Your application should be [[Development/Tutorials/Localization/i18n|completely translatable]].
-When you decide you want to move to this second stage, move your application to {{path|/trunk/kdereview}} and announce the move on '''kde-core-devel@kde.org'''. In the announcement address the above issues and state where you want your application to move to (which KDE main module or extragear). Extragear only requires general approval on kde-core-devel. A main module requires approval from the community who manages that module (e.g. the kdepim module requires approval from the kdepim community). Don't forget to move the documentation of your application to {{path|/trunk/kdereview/doc}}
+When you decide you want to move to this second stage, move your application to {{path|/trunk/kdereview}} and announce the move on '''kde-core-devel@kde.org'''. In the announcement address the above issues and state where you want your application to move to (which KDE main module or extragear). Extragear only requires general approval on kde-core-devel. A main module requires approval from the community who manages that module (e.g. the kdepim module requires approval from the kdepim community). Don't forget to move the documentation of your application to {{path|/trunk/kdereview/doc}}. Some suggestions for reviewers to consider when reviewing new applications and library code are on [[Policies/Suggested_Review_Criteria]].
 The move to kdereview starts a two week review period during which the community can object to your proposal or request additional changes. If there are no objections or requested changes after this two week period, you are allowed to move your application to the place you requested. If your intention is to move to a main module you must additionally get approval from the [[Projects/Release_Team#Module_Coordinators|module coordinator(s)]] who manage that module.