Re: [Firebird-devel] Issues addressed in RC5

[Dmitry Y. <di...@us...>]

"Jim Behr" <ji...@gm...> wrote:
>
> I was looking at the current road map for the Firebird core (
> http://tracker.firebirdsql.org/browse/CORE?report=com.atlassian.jira.plugin.system.project:roadmap-panel).
> The issue that we had identified (
> http://tracker.firebirdsql.org/browse/CORE-902) which causes a server 
> crash
> is not included in the plan for RC5 but instead is scheduled to be in the
> 2.1 release.

Usually, any known bug is being fixed in HEAD first. As soon as it's fixed 
there, it appears in the v2.1 roadmap. And only then it's considered for 
backporting into the release branch and, if positive, it changes its status 
to "fixed in v2.0 RC5" and hence moves to another roadmap. In your case, the 
fix hasn't been backported yet, although agreed to.

> I understand the desire to minimize changes in what will
> hopefully be the final 2.0 release.  However, not including a fix for a
> known server crash does not make sense to me.

Release Candidates fix only regressions, i.e. fixes for old bugs are not 
included there. This prevents us from having an infinite RC stage. However, 
there may be exceptions from this rule if the issue is considered important 
enough. Bug CORE-902 is not a regression per se (it was in the code since 
the Borland era), but it becomes more visible now due to the changes in the 
garbage collection logic. We consider it an implicit regression and hence 
the fix will be included in RC5.


Dmitry