teams:release
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
teams:release [2020-11-22 02:54] – [Suggestion for Dokuwiki Release documentation] Fred23 | teams:release [2020-11-22 07:00] (current) – old revision restored (2014-02-27 02:25) Aleksandr | ||
---|---|---|---|
Line 2: | Line 2: | ||
The Release Management Team, as the name suggests, takes care of organizing the whole release process and prepare the release packages. | The Release Management Team, as the name suggests, takes care of organizing the whole release process and prepare the release packages. | ||
+ | ===== What skills are needed? ===== | ||
+ | * Communication and Organization skills to organize the joined efforts of all teams during a release | ||
+ | * Some knowledge about [[devel: | ||
+ | * Knowledge about writing shellscripts (to automate build tasks) might help | ||
===== What are the main Tasks? ===== | ===== What are the main Tasks? ===== | ||
Line 11: | Line 15: | ||
* handle [[devel: | * handle [[devel: | ||
* manage [[devel: | * manage [[devel: | ||
+ | ===== Who are we? ===== | ||
+ | | {{ http:// | ||
+ | | {{ http:// | ||
+ | | {{ http:// | ||
+ | ===== Current Tasks ===== | ||
+ | |||
+ | * make a definite release plan and do the release of "Lazy Sunday" | ||
+ | * managing DokuWiki on a stick? Are there any other public derivatives of DokuWiki? ICKEWiki? At least coordinate derivatives | ||
+ | * should we make the [[install: | ||
+ | * Handling Plugin-Wizard? | ||
+ | |||
+ | ===== Suggestion for Dokuwiki Release documentation ===== | ||
+ | |||
+ | Here's how the [[http:// | ||
+ | |||
+ | They use bugzilla for bugs and feature requests. These bugs are assigned to (or taken by, I don't know) people responsible for solving the bug or planning the implementation of the feature request. A bug is confirmed through testing, then in development, | ||
+ | |||
+ | All finished bugs are targeted to the next release. | ||
+ | |||
+ | After some time it's feature-freeze time and all feature requests "in progress" | ||
+ | |||
+ | When the Zimbra release team thinks, " | ||
+ | |||
+ | After some time, the release gets GA (globally available) and makes it to the download page. | ||
+ | |||
+ | Now something brilliant: They have this product management site ([[http:// | ||
+ | |||
+ | I think, that this bug and release management is brilliant, productive and very professional and we should follow that as a guideline. I don't know my way around github' | ||
+ | |||
+ | If not, we could move the bug managment to bugzilla (or whatever else, Mantis comes to mind...) and speak with the guys of the admin team about it. (Hey! Just remembered, I'm one of them :) ) | ||
+ | |||
+ | -- Dennis Ploeger, 2010-10-07 20:24 | ||
+ | |||
+ | Bummer! Somehow I forgot, that you people are working with flyspray. Sorry. So, what about actively using the release planning feature of flyspray? | ||
+ | |||
+ | -- Dennis Ploeger, 2010-10-08 07:35 | ||
+ | |||
+ | > Actually, we are using it: http:// |
teams/release.txt · Last modified: 2020-11-22 07:00 by Aleksandr