some release caveats, some todos

Original commit message from CVS:
some release caveats, some todos
This commit is contained in:
Andy Wingo 2002-02-02 23:09:20 +00:00
parent 259c8c394c
commit e9ea094528
2 changed files with 36 additions and 13 deletions

14
TODO
View file

@ -1,13 +1,13 @@
- property proxy in compount elements. - property proxy in compount elements.
- plugable schedulers. - implement events in all plugins.
- implement events in plugins.
- app must be able to catch events? - app must be able to catch events?
- caps nego
- propagation of errors in plugins.
- deal with clocking issues - deal with clocking issues
- use real chaining where possible - use real chaining where possible
- factory aliases? - factory aliases?
- fix plugins :
wtay : the proper fix is of course to fix the plugins and * gst_elementfactory_make ("factoryname", NULL) automatically uniquifies the name
implement the cleanup in the state change function.. * a plugin test rig
* parser and scheduler test system
* clean up xml code - restore/save creates/save pipeline, gst_object_save/load_props
with just the properties

View file

@ -1,17 +1,24 @@
maybe we should be doing releases on branches from the trunk so that the package
version in CVS can always be date-generated and core hacking isn't discouraged
during the release cycle.
Release TODO Release TODO
------------ ------------
* make distcheck should pass
* rpms should build
* debs should build
Packaging issues will hopefully be less difficult in the future as the build
system stabilizes.
* after a release, we move in cvs mode and use a .1 nano version number * after a release, we move in cvs mode and use a .1 nano version number
* close to the next release, we make prereleases by upping the nano version * close to the next release, we make prereleases by upping the nano version
* update release notes
* add release notes to cvs
* update web site release notes * update web site release notes
* make distcheck should pass * add release notes to cvs -- why?
* test suite should pass * test suite should pass
@ -25,19 +32,35 @@ Release TODO
* update package version * update package version
* roll a preliminary distribution tarball, make sure that it installs fine,
registers fine, runs the media tests fine, and uninstalls as well
* tag tree * tag tree
http://gstreamer.net/dev/cvs.php http://gstreamer.net/dev/cvs.php
add tag to above page add tag to above page
* update web site release notes: added to cvs
- change the releases/current symbolic link
- text version of release announcement can be made from
lynx -dump http://gstreamer.net/releases/current/notice.php?clean=1
* update web site docs
- release-specific docs should go in CVS
- change docs/current symlink
* update status table cvs status and then click on the release link
http://gstreamer.net/admin.php is the portal to all of this
* update web site news items for release * update web site news items for release
again, the admin.php page
* upload to sourceforge * upload to sourceforge
- should we md5 the tarballs?
* announce to: * announce to:
freshmeat freshmeat
gstreamer-{devel, announce} gstreamer-{devel, announce}
linux-audio-dev (?) linux-audio-dev (if it's a big release)
gnome lists (?) gnome lists (?)
lwn (if it's a big release) lwn (if it's a big release)