blob: fdf1ec4ddef77c2067e09a469d578f89dfee3a07 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
|
Release TODO
------------
* 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
* update release notes
* add release notes to cvs
* update web site release notes
* make distcheck should pass
* test suite should pass
* autotools have latest config.{guess,sub}
This is needed in order to support newer platforms.
On Debian install the autotools-dev package to get these.
* depending on how the API has changed update the libtool versioning
in configure.ac. Look at the libtool info page about versioning for
guidelines.
* update package version
* tag tree
http://gstreamer.net/dev/cvs.php
add tag to above page
* update web site news items for release
* upload to sourceforge
* announce to:
freshmeat
gstreamer-{devel, announce}
linux-audio-dev (?)
gnome lists (?)
lwn (if it's a big release)
Should work:
* autoconf feature to allow building outside source dir
Package version policy
----------------------
Use major.minor.micro versioning
Before 1.0.0
Update micro until code and API are fairly stable, then update minor.
After 1.0.0
Update major when code and api hit new level of stability or major features.
Update minor on API changes.
Update micro on API-compatible changes.
|
