CITATION.bib from metapackage

[1ucian0]

Originally posted by @garrison in Qiskit/qiskit-metapackage#1722 (comment)

Just noticed that CITATION.bib needs to move as well. Otherwise, the link from the Terra README will be broken after qiskit-terra -> qiskit.

This is related with RFC 0011

[qiskit-bot]

One or more of the the following people are requested to review this:

• @Qiskit/terra-core

[coveralls]

Pull Request Test Coverage Report for Build 4973761157

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 21 unchanged lines in 6 files lost coverage.
• Overall coverage decreased (-0.04%) to 85.862%

---

Files with Coverage Reduction	New Missed Lines	%
crates/qasm2/src/expr.rs	1	93.76%
qiskit/extensions/quantum_initializer/squ.py	2	80.0%
crates/accelerate/src/vf2_layout.rs	3	94.74%
crates/accelerate/src/sabre_swap/layer.rs	4	97.32%
crates/qasm2/src/lex.rs	5	90.63%
crates/qasm2/src/parse.rs	6	97.58%

Totals
Change from base Build 4961195397:	-0.04%
Covered Lines:	70814
Relevant Lines:	82474

---

💛 - Coveralls

[garrison]

Thanks. I grepped terra for .bib, and this is indeed the only occurrence. The only change I suggest is editing .md -> .bib in this PR's title, to avoid confusion when viewing the shortlog.

[ikkoham]

This comes from the original file in qiskit-metapacage, but why is the year 2023? and do we plan to update every year?

[Cryoris]

I would expect this to match the version users cite -- so I would think we have to update it every year. But I also don't know what the common practice for this is 🙂

[jakelishman]

I believe that the Zenodo DOI in the citation will point to the latest release, so the year of the most recent release should be correct in general, I think.

[jakelishman]

This seems fine to me. We'll potentially want to have qiskit-bot update the year for us on the first release of a new year, if necessary, but any change on that front is done elsewhere, and might depend on what automation we remain with after the repository switch-over.