On 5 January 2016 at 22:53, Philippe Mouawad <[email protected]> wrote: > I created a bugzilla for this.
However it is not mentioned on the original BZ. > It is to make release notes clear. Fixing deprecations should be part of any library version upgrades. Otherwise it's not a complete fix. Fixing deprecations as part of a version upgrade need not (in fact should not) be separately documented in changes.xml. Indeed it would be more confusing to show deprecation removal separately in this case. [However if deprecations were left over from a previous release, it probably would make sense to add a changes record] > If you keep it open, then do you remove it from changes.xml while we indeed > changed version and migrated cookiemanager ? Provided that the work is done before the release is cut, I see no reason to remove the text from changes.xml temporarily. > > > On Tuesday, January 5, 2016, <[email protected]> wrote: > >> https://bz.apache.org/bugzilla/show_bug.cgi?id=57319 >> >> Sebb <[email protected] <javascript:;>> changed: >> >> What |Removed |Added >> >> ---------------------------------------------------------------------------- >> Resolution|FIXED |--- >> Status|RESOLVED |REOPENED >> >> --- Comment #4 from Sebb <[email protected] <javascript:;>> --- >> There are lots of deprecation warnings still to fix. >> >> -- >> You are receiving this mail because: >> You reported the bug. >> You are on the CC list for the bug. >> > > > -- > Cordialement. > Philippe Mouawad. > Ubik-Ingénierie > > UBIK LOAD PACK Web Site <http://www.ubikloadpack.com/> > > UBIK LOAD PACK on TWITTER <https://twitter.com/ubikloadpack>
