Re: [sdcc-devel] The next release

[Borut R. <bor...@gm...>]

So it is not necessary to make the release branch at the release time, 
but it can be created afterwards from the release tag (or release svn 
revision) if needed. So nothing changes regarding the current situation. 
The only problem is to make a build from a given branch (or svn 
revision) instead from the svn head. This was supported by the build 
process in the past (in CVS era), but I doubt that it woks any more.

And there is an other potential difficulty: since it is not known in 
advance whether a "quick release" will be necessary, the bug fixes will 
normally be committed to the main branch, which means that they'll have 
to be back-ported to the release branch if necessary.

Borut

On 06/05/2011 05:04 PM, Philipp Klaus Krause wrote:
> Am 05.06.2011 16:51, schrieb Borut Razem:
>
>> This means that we have to make a release svn branch, which I was trying
>> to avoid in the past...
>> How would you call this two releases? You have to call them differently
>> in order to distinguish them. So the first one will be "pre-release" and
>> the second one will be "release". But the users will again not install
>> the "pre-release" since they will be wainting for the final "release".
>> And this is exactly where we are now, just rename "pre-release" to RCx.
> I just would call them releases, they would have to have different
> version numbers to distinguish them. The one month in between probably
> shouldn't be a fixed time. If there are more bugs we might need longer,
> if there are no grave bugs we just wouldn't do the second release.
>
> Philipp
>