14.03.2013 11:48, Alex Peshkoff wrote: > I see no problems building packages with this patch. It's really > trivial, and if packages are based on previous tags (2.1.5/2.5.2), not > branches, they do not require QA and release notes, they can be released > with just single note: "Fixed severe security vulnerability".
I believe a new tag should be created based on the already released one with the patch added. Something like R2_1_5_sec_1 and R2_5_2_sec_1. And I'm afraid a new revision of the release notes would be needed if we want to have the bugfix properly documented. > What I do not understand - what number will get that release? It's > definitely not 2.5.3. May be Firebird-2.5.2.26540-1? (We had > Firebird-2.5.2.26539-0). This may cause confusion with Firebird-2.5.3.26540 which does not have the bug fixed. But I'm out of better ideas. Dmitry ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
