author | Raman Gupta <raman@rocketraman.com> | |
Thu, 12 Nov 2009 19:46:04 +0000 (14:46 -0500) | ||
committer | Junio C Hamano <gitster@pobox.com> | |
Sat, 21 Nov 2009 07:39:58 +0000 (23:39 -0800) | ||
commit | 382e54312220ac02586a3cbb06b0e4eb7789f043 | |
tree | 1736711f8d4558b0ce65826659dfd3255fc755f8 | tree | snapshot |
parent | 78d553b7d7b269bb22ebd8b1198657c37484a3a0 | commit | diff |
Add branch management for releases to gitworkflows
The current man page does a reasonable job at describing branch management
during the development process, but it does not contain any guidance as to
how the branches are affected by releases.
Add a basic introduction to the branch management undertaken during a
git.git release, so that a reader may gain some insight into how the
integration, maintenance, and topic branches are affected during the
release transition, and is thus able to better design the process for their
own project.
Other release activities such as reviews, testing, and creating
distributions are currently out of scope.
Signed-off-by: Nanako Shiraishi <nanako3@lavabit.com>
Acked-by: Thomas Rast <trast@student.ethz.ch>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
The current man page does a reasonable job at describing branch management
during the development process, but it does not contain any guidance as to
how the branches are affected by releases.
Add a basic introduction to the branch management undertaken during a
git.git release, so that a reader may gain some insight into how the
integration, maintenance, and topic branches are affected during the
release transition, and is thus able to better design the process for their
own project.
Other release activities such as reviews, testing, and creating
distributions are currently out of scope.
Signed-off-by: Nanako Shiraishi <nanako3@lavabit.com>
Acked-by: Thomas Rast <trast@student.ethz.ch>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Documentation/gitworkflows.txt | diff | blob | history |