From: Borut R. <bor...@gm...> - 2011-10-15 22:04:01
|
On 10/15/2011 11:09 PM, Philipp Klaus Krause wrote: > How about: > > SDCC 3.2.0 RC1: 2011-12-30 > SDCC 3.2.0 RC2: 2012-1-6 > SDCC 3.2.0 Release: 2012-1-13 > > With no big changes, except for bug fixes commited between 3.1.0 release > and 3.2.0 rc1? > > Due to the large number of commits between 3.0 and 3.1 I expect many bug > regression bug reports to come in after the 3.1 release has been picked > up by distributions. Once those have been fixed we will have a much more > stable sdcc in trunk (at least that's waht I've seen with previous > releases) that then gradually accumulates bugs over time. The release in > january would give users the temporary stability from post-release trunk > in a release. We already discussed about this and I agree, even that it is not so easy: we will probably have to make a branch from 3.1.0, containing only critical fixes, without the new functionality. Making release packages means convincing snapshot build machines to make builds from a branch instead from the svn HEAD, since releases are nothing else the repacked snapshot builds. And I'm afraid that this is currently not supported (at least not tested). The other option is to delay the new functionality merging until the 3.2.0 is released... But let first make the 3.1.0 release, then we will see... Borut |