[asterisk-dev] Thoughts on Asterisk release management

Donny Kavanagh donnyk at gmail.com
Wed Sep 19 21:26:26 CDT 2007


Much like josh i'll start a clean slate here such that the email
doesnt become horrendously long.

Russ & Josh, i totally agree.  The only comment i have is for those
not familiar with the odds / events versioning system which means
evens release versions, odd's dev versions.  We should be clear to
label them as such so there is no confusion in thinking 1.5 super
cedes 1.4 for production use.   It may be wise to use 'dev' or
'testing' in the tar ball release names.  Eg, rather then
asterisk-1.5.0.tar.gz instead asterisk-1.5.0-dev.tar.gz or
asterisk-1.5.0-testing.tar.gz also a warning should be added to the
makefile to also display this on a make/make install.  Personally i'd
argue that the 1.5.x releases should only be tags on SVN but then that
would likely limit the testing it would receive.

Other then making sure this is clear i agree wholeheartedly.

Russ, i suggest picking a start date in the future and doing up from
that point a proposed development calendar including freezes,
releases, etc.

Donny/Juggie



More information about the asterisk-dev mailing list