docs/random/release: Move the current documentation of how to do a release to the top of the file.

Original commit message from CVS:
* docs/random/release:
Move the current documentation of how to do a release to the top
of the file.

* gst/gstbin.c: (gst_bin_class_init),
(gst_bin_handle_message_func):
Allow multiple state-recalculation threads. (Closes #328873)
This commit is contained in:
Jan Schmidt 2006-02-20 12:26:50 +00:00
parent 34a3b80747
commit a54323429c
3 changed files with 62 additions and 42 deletions

View file

@ -1,3 +1,13 @@
2006-02-20 Jan Schmidt <thaytan@mad.scientist.com>
* docs/random/release:
Move the current documentation of how to do a release to the top
of the file.
* gst/gstbin.c: (gst_bin_class_init),
(gst_bin_handle_message_func):
Allow multiple state-recalculation threads. (Closes #328873)
2006-02-19 Julien MOUTTE <julien@moutte.net>
* gst/gstinfo.h: Add GST_STR_NULL to the second string.

View file

@ -30,6 +30,50 @@ interested developers. To minimize the impact on the rest of the core hacking,
we create a new CVS branch which will go through the pre-releases and finally
contain the definitive tarball for that version.
RELEASE PROCEDURE:
-----------------
- www/bin/new-release is a release helper script. It automates a lot of the
tedious work. Now releasing looks like this:
- before release:
- make sure all blocker bugs for that release are fixed or deferred
- make sure you have a local copy of all online files
- bin/new-release (module) (version) (checkoutdir) (release name)
- updates cvs
- allows you to update versioning in configure.ac
- rebuilds
- updates ChangeLog
- adds a new releases/module/version.xml file and lets you edit
--> here you add/fix up the features (from ChangeLog) and check
contributors
- allows you to update NEWS file with snippets from RELEASE
--> copy stuff
- rebuilds docs for plugins
- rolls release tarballs and puts them in the local www/data tree
- uploads docs to website
- commits changes to po files
- shows you a diff for evaluation
- build packages to test
- release:
- cvs commit in the tree
- tag tree
for example for 0.6.3 :
cvs tag RELEASE-0_6_3
- bump nano number, commit
- if working in the "stable" release branch, update to this tag to freeze it:
cvs up -r RELEASE-0_6_3
- sync source and packages to website
- add entry on website; commit additions to website
- change versions in www/src/htdocs/entities.gst
- add versions and milestones in bugzilla
Old release notes - superceded by the www/bin/new-release script.
----------------------------------------------------------------
TODO :
- Decide on the next version number (major, minor or micro upgrade ?)
- Get a fresh copy to do the necessary tests on
@ -195,44 +239,5 @@ NOTES ON STARTING A NEW STABLE SERIES
NEW NOTES
---------
- www/bin/new-release is a release helper script. It automates a lot of the
tedious work. Now releasing looks like this:
- before release:
- make sure all blocker bugs for that release are fixed or deferred
- make sure you have a local copy of all online files
- bin/new-release (module) (version) (checkoutdir) (release name)
- updates cvs
- allows you to update versioning in configure.ac
- rebuilds
- updates ChangeLog
- adds a new releases/module/version.xml file and lets you edit
--> here you add/fix up the features (from ChangeLog) and check
contributors
- allows you to update NEWS file with snippets from RELEASE
--> copy stuff
- rebuilds docs for plugins
- rolls release tarballs and puts them in the local www/data tree
- uploads docs to website
- commits changes to po files
- shows you a diff for evaluation
- build packages to test
- release:
- cvs commit in the tree
- tag tree
for example for 0.6.3 :
cvs tag RELEASE-0_6_3
- bump nano number, commit
- if working in the "stable" release branch, update to this tag to freeze it:
cvs up -r RELEASE-0_6_3
- sync source and packages to website
- add entry on website; commit additions to website
- change versions in www/src/htdocs/entities.gst
- add versions and milestones in bugzilla

View file

@ -348,7 +348,7 @@ gst_bin_class_init (GstBinClass * klass)
GST_DEBUG ("creating bin thread pool");
err = NULL;
klass->pool =
g_thread_pool_new ((GFunc) gst_bin_recalc_func, NULL, 1, FALSE, &err);
g_thread_pool_new ((GFunc) gst_bin_recalc_func, NULL, -1, FALSE, &err);
if (err != NULL) {
g_critical ("could alloc threadpool %s", err->message);
}
@ -2005,8 +2005,13 @@ gst_bin_handle_message_func (GstBin * bin, GstMessage * message)
klass = GST_BIN_GET_CLASS (bin);
gst_object_ref (bin);
GST_DEBUG_OBJECT (bin, "pushing recalc on thread pool");
g_thread_pool_push (klass->pool, bin, NULL);
if (!bin->polling) {
GST_DEBUG_OBJECT (bin, "pushing recalc on thread pool");
g_thread_pool_push (klass->pool, bin, NULL);
} else {
GST_DEBUG_OBJECT (bin,
"state recalc already in progress, not pushing new recalc");
}
GST_OBJECT_UNLOCK (bin);
break;