User:Winterz - Revision history

Winterz: Blanked the page

2012-05-06T21:35:07Z

Blanked the page

Winterz: /* kdelibs Package Dependencies */

2012-05-06T21:34:56Z

‎kdelibs Package Dependencies

Show changes

Winterz at 20:40, 6 May 2012

2012-05-06T20:40:42Z

Winterz: /* KDE SC Release Packaging Thoughts */

2012-05-06T17:35:29Z

‎KDE SC Release Packaging Thoughts

Show changes

Winterz: /* KDE SC Release Packaging Thoughts */

2012-04-27T22:16:27Z

‎KDE SC Release Packaging Thoughts

Winterz: /* KDE SC Release Packaging Thoughts */

2012-04-27T22:15:34Z

‎KDE SC Release Packaging Thoughts

Winterz at 21:46, 27 April 2012

2012-04-27T21:46:57Z

Winterz: /* KDE SC Release Packaging Thoughts */

2012-04-27T21:07:26Z

‎KDE SC Release Packaging Thoughts

Winterz at 21:04, 27 April 2012

2012-04-27T21:04:02Z

Winterz: Removing all content from page

2008-02-01T13:07:42Z

Removing all content from page

← Older revision		Revision as of 21:35, 6 May 2012
Line 1:		Line 1:
−	~~The following was generated using a perl program I wrote that reads the CMakeLists.txt files in kdelibs.~~	+

@@ Line 1: / Line 1: @@
-= KDE SC Release Packaging Thoughts =
+The following was generated using a perl program I wrote that reads the CMakeLists.txt files in kdelibs.
-−
-. the Continuous Integration (CI) System
-  - all the KDE SC modules are built continuously
-  - no packaging unless all modules build ok
-    (even better would be to force all make tests too)
-  - the packaging tools run on the CI system generating "test" tarballs
-  - the "test" tarballs could be downloaded from the CI system
-−
-−
-. the KDE Sysadmin Team
-  - provides and manages the CI system
-  - will transfer "test" tarballs to the public ftp site
-  - prepares the public ftp site for bandwidth requirements at release announce time
-−
-−
-. the KDE Promo Team
-  - writes and distributes release announcements through normal channels
-  - deals with the media
-  - manages public expectations
-−
-−
-. the KDE i18n Team
-  - maintains the languages list
-−
-−
-. the KDE Release Team
-  - coordinates the entire release effort
-  - sets release milestones and dates
-  - communicates important dates to the community and to distros
-  - communicates important news to the community and to distros
-  - creates "test" tarballs using the CI system and handles distro feedback
-  - adds hot and security patches to the tarballs before the final release
-  - creates "final" tarballs using the CI system
-  - pushes tags to the module repositories in a timely manner
-  - writes and maintains the necessary tools
-  - writes and maintains the release process documentation
 == kdelibs Package Dependencies ==

@@ Line 1: / Line 1: @@
 = KDE SC Release Packaging Thoughts =
-. the CI System
+. the Continuous Integration (CI) System
    - all the KDE SC modules are built continuously
    - no packaging unless all modules build ok

@@ Line 5: / Line 5: @@
    - no packaging unless all modules build ok
      (even better would be to force all make tests too)
-   - the packaging tools run on the CI system generating "test" tarballs.
+   - the packaging tools run on the CI system generating "test" tarballs
    - the "test" tarballs could be downloaded from the CI system
+   -
@@ Line 35: / Line 35: @@
    - pushes tags to the module repositories in a timely manner
    - writes and maintains the necessary tools
-   - writes and documents the release process
+   - writes and maintains the release process documentation

@@ Line 1: / Line 1: @@
 = KDE SC Release Packaging Thoughts =
-. a CI system where we build all of KDE SC
+. the CI System
    - no packaging unless all modules build ok
      (even better would be to force all make tests too)
@@ Line 29: / Line 30: @@
    - communicates important dates to the community and to distros
    - communicates important news to the community and to distros
-   - creates "test" tarballs using the CI system and handles feedback
+   - creates "test" tarballs using the CI system and handles distro feedback
    - adds hot and security patches to the tarballs before the final release
    - creates "final" tarballs using the CI system

← Older revision	Revision as of 21:04, 27 April 2012
Line 1:	Line 1:
	+	= KDE SC Release Packaging Thoughts =

	+	1. a CI system where we build all of KDE SC
	+	- no packaging unless all modules build ok
	+	(even better would be to force all make tests too)
	+	- the packaging tools run on the CI system generating "test" tarballs.
	+	- the "test" tarballs could be downloaded from the CI system
	+	-
	+
	+	2. the KDE Sysadmin Team
	+	- provides and manages the CI system
	+	- will transfer "test" tarballs to the public ftp site
	+	- prepares the public ftp site for bandwidth requirements at release announce time
	+	-
	+
	+	3. the KDE Promo Team
	+	- writes and distributes release announcements through normal channels
	+	- deals with the media
	+	- manages public expectations
	+	-
	+
	+	4. the KDE i18n Team
	+	- maintains the languages list
	+	-
	+
	+	* the KDE Release Team
	+	- coordinates the entire release effort
	+	- sets release milestones and dates
	+	- communicates important dates to the community and to distros
	+	- communicates important news to the community and to distros
	+	- creates "test" tarballs using the CI system and handles feedback
	+	- adds hot and security patches to the tarballs before the final release
	+	- creates "final" tarballs using the CI system
	+	- pushes tags to the module repositories in a timely manner
	+	-

← Older revision		Revision as of 13:07, 1 February 2008
Line 1:		Line 1:
−	~~== My Lists and Tables of Stuff ==~~
−	~~Welcome to my world.~~

−	~~===Minimum Requirements before a KDE 4.0.0 Release Candidate===~~
−	* a functional workspace
−	** Plasma (aseigo)
−	** color configuration works (mwoehlke)
−	* oxygen style working (mwoehlke, boemann, #oxygen)
−	* konqueror working
−	* dolphin working (Peter Penz)
−	* sound working (Vir)
−	* kmail working (till, tmg)
−	* kate working
−
−	~~"working" doesn't mean "bug free"; it means no known "grave bugs".~~
−	~~"working" means using it doesn't make you want throw your computer out the window.~~
−
−	~~=== Bugs Encountered ===~~
−	~~{\| border="1"~~
−	~~\|+ Known Bugs~~
−	\|-
−	~~! Application~~
−	~~! Issue~~
−	~~! Status~~
−	\|-
−	~~\| dolphin~~
−	~~\| nepomukdaemon not autostarted~~
−	~~\| $XDG_DATA_DIRS not appropriately set before dbus-launch is started (thiago)~~
−	\|-
−	~~\| strigiclient~~
−	~~\| strigidaemon not autostarted~~
−	~~\| $XDG_DATA_DIRS not appropriately set before dbus-launch is started (thiago)~~
−	\|-
−	~~\| strigiclient~~
−	~~\| thinks that strigidaemon is running when it isn't~~
−	~~\| reported to Jos~~
−	\|-
−	~~\| strigiclient~~
−	~~\| when creating index, cannot find any fields in .fieldproperties ontology database~~
−	~~\| reported to Jos~~
−	\|-
−	~~\| kbackgammon~~
−	~~\| writes "KNotificationManager::notify:: error while contacting knotify server" to konsole.~~
−	~~\| probably must be ported from KDE3's KNotifyClient to KDE4's new KNotification~~
−	\|-
−	~~\| kate~~
−	~~\| regex search/replace skips matches and can even do endless loops in some cases(?), sorry :-( Bug must be somewhere in my KateDocument code.~~
−	~~\| sping already knows~~
−	\|-
−	\|}