Contribution
Casper Langemeijer <[email protected]> Fri, 15 Mar 2019 11:15:44 +0100
| Newsgroups | gmane.mail.imap.dbmail.devel |
|---|---|
| Message-ID | <CAE4uwN6CR7ru0_K=BtT_3-JfYpK+=nznqvJfSD3a-NWgV43hRQ@mail.gmail.com> |
--===============7650550683913043781== Content-Type: multipart/alternative; boundary=000000000000ff6ff205841f5257 --000000000000ff6ff205841f5257 Content-Type: text/plain; charset="UTF-8" Hi All, I have some good news. My employer has decided that it would be a good idea to bring a new dbmail version to production. This means I have a full work-week in which I can contribute to the dbmail project. This will start April 10th. For my employer gmime3 and new debian packaging is a necessity and a precondition to donate the hours I make. I created PR's on these issues for everyone to comment on. https://github.com/dbmail/dbmail/pulls It would be nice to have a clear list of pull requests that could make it to the next release. In my personal time I will have a look at https://github.com/pjstevns/dbmail/pulls and see what changes are there that I can support. If you have a PR in that list I will probably ask you some questions in the near future. If you feel you can do some work on them you could also create a new PR to the dbmail/dbmail repo. (If you forked from pjstevns/dbmail, making a PR to dbmail/dbmail is not easy. I created a new fork from dbmail/dbmail, transferred my branches locally, pushed them and then created my new PR's) Starting April 10th I will try to merge as much PR's into a releasable branch, a release candidate if you will. I will do tests, some load-testing and generally make sure this is suitable for production. My focus will be on amd64 on linux. In this week I will bring this release candidate into production on our own servers. After this week in my own time I will still make contributions and work to get the release candidate into a proper release. What are your opinions on this? Are there any concerns I should be thinking about, that I might have missed? If any of you feel you can contribute and want to do more synchronized communication on it we can probably do a IRC or slack channel or something. I am open for any suggestions. Greetings, Casper --000000000000ff6ff205841f5257 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Hi All,<div><br></div><div>I have some good news. My emplo= yer has decided that it would be a good idea to bring a new dbmail version = to production. This means I have a full work-week in which I can contribute= to the dbmail project. This will start April 10th.=C2=A0</div><div><br></d= iv><div>For my employer gmime3 and new debian packaging is a necessity and = a precondition to donate the hours I make. I created PR's on these issu= es for everyone to comment on.=C2=A0<a href=3D"https://github.com/dbmail/db= mail/pulls">https://github.com/dbmail/dbmail/pulls</a></div><div><br></div>= <div>It would be nice to have a clear list of pull requests that could make= it to the next release. In my personal time I will have a look at <a href= =3D"https://github.com/pjstevns/dbmail/pulls">https://github.com/pjstevns/d= bmail/pulls</a>=C2=A0and see what changes are there that I can support. If = you have a PR in that list I will probably ask you some questions in the ne= ar future. If you feel you can do some work on them you could also create a= new PR to the dbmail/dbmail repo. (If you forked from=C2=A0pjstevns/dbmail= , making a PR to dbmail/dbmail is not easy. I created a new fork from dbmai= l/dbmail, transferred my branches locally, pushed them and then created my = new PR's)</div><div><br></div><div>Starting April 10th I will try to me= rge as much PR's into a releasable branch, a release candidate if you w= ill. I will do tests, some load-testing and generally make sure this is sui= table for production. My focus will be on amd64 on linux. In this week I wi= ll bring this release candidate into production on our own servers.</div><d= iv><br></div><div>After this week in my own time I will still make contribu= tions and work to get the release candidate into a proper release.</div><di= v><br></div><div>What are your opinions on this? Are there any concerns I s= hould be thinking about, that I might have missed? If any of you feel you c= an contribute and want to do more synchronized communication on it we can p= robably do a IRC or slack channel or something. I am open for any suggestio= ns.</div><div><br></div><div>Greetings, Casper</div></div> --000000000000ff6ff205841f5257-- --===============7650550683913043781== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KRGJtYWlsLWRl diBtYWlsaW5nIGxpc3QKRGJtYWlsLWRldkBkYm1haWwub3JnCmh0dHA6Ly9saXN0cy5uZmcubmwv bWFpbG1hbi9saXN0aW5mby9kYm1haWwtZGV2Cg== --===============7650550683913043781==--