Hi Mateusz,

First and foremost, thanks for all your work on SOCI.

I use SOCI for several projects, and I also maintain the SOCI packages
in Debian.  While I can't commit to assisting with development of new
features and such (due to time constraints), I'd be happy to assist with
bug fixes, etc. as need arises.

Best regards,
Bill



On Tue, Dec 17, 2019 at 11:35:07AM +0100, Mateusz Loskot wrote:
> On Mon, 16 Dec 2019 at 18:31, Vadim Zeitlin <vz-s...@zeitlins.org> wrote:
> > On Fri, 13 Dec 2019 22:31:06 +0100 Mateusz Loskot <mate...@loskot.net> 
> > wrote:
> >
> > ML> Congratulations all and my special thanks go to Vadim Zeitlin
> > ML> for his continuous contributions and support.
> >
> >  I'm a bit ashamed to read this because I've been telling myself that I
> > really should have helped you much more with this, but I just could never
> > find time/motivation/energy to do it, so thanks a lot for pulling it out
> > this release on your own!
> 
> No need to be ashamed. Whenever it was needed, you've been supportive.
> 
> > ML> Anyone who is actively interested in the development of SOCI,
> > ML> you can shape the future of the project, you can maintain it,
> > ML> you can release it.
> > ML>
> > ML> I still hold keys giving access to numerous knobs in the project,
> > ML> CI services, SourceForge services, and other admin areas.
> > ML>
> > ML> If anyone is interested in becoming the project maintenance,
> > ML> please stepping forward here on the list and I will be happy
> > ML> to hand over the "reins".
> >
> >  I definitely remain interested in _using_ SOCI as we rely on it, so even
> > though I'm probably not going to spend much time on developing it further,
> > as the current version serves our needs sufficiently well, I still want it
> > to live on, so I'm prepared to do whatever is needed to maintain it, i.e.
> > merge PRs, eventually update it to C++11 (well, C++20 by the time I get to
> > it, probably) etc.
> 
> This is very good news for SOCI. Thank you!
> 
> >  The release process seems to be well documented in RELEASING.md (thanks!),
> > but I guess it would be best if I could follow it at least once in order to
> > ensure that I can do everything involved. We already have 1 PR applied to
> > master since 4.0.0 and another simple one (fixing Oracle buffer size)
> > waiting to be applied and I have a couple of Oracle changes/fixes myself
> > too, so I suggest that I try to make a 4.0.1 release some time soon, with
> > all these fixes in it, but mostly just to test the release process, what do
> > you think?
> 
> This is a good idea.
> 
> I'll stick around and whenever you need assistance
> just post here or mention me on GitHub.
> 
> >  Thanks again for all your work on SOCI and I still owe you a beer (or
> > another beverage of your choice), please drop me a note if you pass by
> > Paris!
> 
> Thanks, I certainly will!
> 
> Best regards,
> -- 
> Mateusz Loskot, http://mateusz.loskot.net
> 
> 
> _______________________________________________
> soci-devel mailing list
> soci-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/soci-devel

-- 
GPG: 5CDD 0C9C F446 BC1B 2509  8791 1762 E022 7034 CF84


_______________________________________________
soci-devel mailing list
soci-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/soci-devel

Reply via email to