[Q-e-developers] Next Quantum ESPRESSO release -- June 20th

[Filippo Spiga]

Dear Satomichi,

before proceed with practical details we need to know few things about your code:
- Which QE version is compatible with it?
- Did you develop 3D-RISM-SCF as external plug-in or directly inside the QE code?
- Do you have extensive tests to validate your implementation?
- Do you have one or more reference papers that explains the method utilized?
- Is your code suitable for general public release under GPL license?
- Are you willingness to maintain and take care of bug fixes and improvements of this particular piece of code for at least one year starting from the release date?

Regards,
Filippo

On Jun 7, 2015, at 12:53 PM, nisihara225 at gmail.com wrote:
> Dear Dr. Filippo Spiga and Dr. Paolo Giannozzi,
> 
> I would like to merge the branch of 3D-RISM-SCF to the truck, and
> integrate it into the next version of Quantum ESPRESSO, which will be released at June 20th.
> If you permit my integration of source codes, please give me advices for integration.
> Especially, I ask for advices about changes and usage corresponding to the “Custom FFT”,
> which is used also in 3D-RISM-SCF.
> 
> Regards,
> Satomichi Nishihara
> 
> 
> 差出人: Filippo Spiga
> 送信日時: ‎2015‎年‎6‎月‎3‎日 ‎水曜日 ‎22‎:‎55
> 宛先: General discussion list for Quantum ESPRESSO developers
> CC: QEF
> 
> Dear QE developers,
> 
> a new release of Quantum ESPRESSO is scheduled for Saturday June 20th. 
> 
> We do not know yet if it going to be 5.1.3 or 5.2, it really depends by an on-going assessment of known bugs being fixed, readiness of new functionalities, stability and availability of third-part codes developer on top of QE common modules and other stuff. Everybody who is contributing in developing packages on top of QE is invited to get in contact via mailing-list or directly to me and Paolo to check compatibility with current code base, support to align code with the latest version or just advices for a better integration.
> 
> Moving forward, we will try to respect fixed dates for future releases. This modus operandi will help everybody to properly schedule their own work since a deadline is enforced. We will continue to use the "X.Y.Z" versioning schema, based on these simple (but flexible) criteria: 
> - bug fixes, minor enhancements... Z+1
> - important bug fixes, major enhancements in parallelization and performance or new physics functionalities in pre-existing packages... Y+1
> - major change in core modules, changes in important routines, brand-new functionalities that affect multiple packages at the same time... X+1
> 
> I am going to update the Quantum ESPRESSO website to publish all release dates scheduled until end of the year. Stuff will appear possibly in the next couple of days.
> 
> If you have any question or you need a bit of help to integrate your code or your changes just get in touch.
> 
> Best Regards,
> Filippo
> 
> --
> Mr. Filippo SPIGA, M.Sc.
> Quantum ESPRESSO Foundation
> http://fspiga.github.io ~ skype: filippo.spiga
> 
> «Nobody will drive us out of Cantor's paradise.» ~ David Hilbert
> 
> *****
> Disclaimer: "Please note this message and any attachments are CONFIDENTIAL and may be privileged or otherwise protected from disclosure. The contents are not to be disclosed to anyone other than the addressee. Unauthorized recipients are requested to preserve this confidentiality and to advise the sender immediately of any error in transmission."
> 
> 
> _______________________________________________
> Q-e-developers mailing list
> Q-e-developers at qe-forge.org
> http://qe-forge.org/mailman/listinfo/q-e-developers

--
Mr. Filippo SPIGA, M.Sc.
http://fspiga.github.io ~ skype: filippo.spiga

«Nobody will drive us out of Cantor's paradise.» ~ David Hilbert

*****
Disclaimer: "Please note this message and any attachments are CONFIDENTIAL and may be privileged or otherwise protected from disclosure. The contents are not to be disclosed to anyone other than the addressee. Unauthorized recipients are requested to preserve this confidentiality and to advise the sender immediately of any error in transmission."