[Qgis-developer] Merging the C_API branch

[Marco Hugentobler]

Hi Frank and Peter,

Thanks for reminding me, I merged the gdal c-api changes to trunk now.
Please apologize the delay, I thought that Frank would merge the branch, 
that's why I didn't do the merge earlier

(from my mail Feb 26:
"So my suggestion is that you go ahead and merge the branch to 
trunk if there is no objection on the devel list in the next two days")

> I must say this "branch for changes then merge" process has not left me
> with warm and fuzzy feelings, and it is hard to imagine my taking it on
> again unless I am contributing to someone else's effort.

Is the delay in merging the reason for the not warm and fuzzy feelings or is 
it something different?

In my opinion, the "branch for changes then merge" process has increased the 
stability of the qgis code considerably and also the release interval is much 
better because of this process (was >1 year before). 

Best regards,
Marco




Am Freitag 14 März 2008 14:58:15 schrieb Frank Warmerdam:
> Peter Ersts wrote:
> > Marco,
> >
> > If there are no outstanding tasks/bugs (I don't think there are) with
> > the C_API branch, would you possibly be able to merge it back into the
> > trunk?  I think it would be a good idea before too many more mods are
> > made to the trunk. Also, I would like to get back to some other raster
> > work but have been procrastinating and holding off until the C_API
> > branch is back in.
>
> Marco,
>
> Yes, I'm also hopeful in this regard.  I will warn that I haven't merged
> back trunk changes into the c-capi branch for a while (2-3 weeks?).
>
> I must say this "branch for changes then merge" process has not left me
> with warm and fuzzy feelings, and it is hard to imagine my taking it on
> again unless I am contributing to someone else's effort.
>
> Best regards,



-- 
Dr. Marco Hugentobler
Institute of Cartography
ETH Zurich
Technical Advisor QGIS Project Steering Committee