Prepare 1.0.0 release

[mtreinish]

Summary

This commit prepares the repo for the 1.0.0 release. It migrates all the release notes to a dedicated directory to differentiate those notes from future notes (this will need to be forward ported to the main branch), updates the version numbers to indicate it is the final 1.0.0 release, and updates the release notes to prepare them for publishing. Once this merges this commit should be used to tag the 1.0.0 release.

Details and comments

TODO:

• Wait for the final PRs of the release to merge
• Finish prelude draft
• Go through and copy-edit and update the release notes

[qiskit-bot]

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

• @Eric-Arellano
• @enavarro51
• @javabster
• @Qiskit/terra-core
• @ajavadia
• @ikkoham
• @levbishop
• @mtreinish
• @nkanazawa1989
• @t-imamichi

[ElePT]

I've taken a look and left some suggestions, hopefully they make sense. I still need to take a look at the release highlights section and last paragraph.

[ElePT]

Part 2

[ElePT]

Maybe link to the rust docs or project repo too?

Suggested change

	* The :class:`.QuantumCircuit` class's internal :attr:`~.QuantumCircuit.data`
	structure has been rewritten in Rust to greatly improve the memory efficiency
	of the :class:`.QuantumCircuit` objects by caching the arguments of the
	instructions.
	* The :class:`.QuantumCircuit` class' internal :attr:`~.QuantumCircuit.data`
	structure has been rewritten in Rust to greatly improve the memory efficiency
	of the :class:`.QuantumCircuit` objects by caching the arguments of the
	instructions.

[mtreinish]

So I think the apostrophe usage here is actually correct as class isn't plural.

As for the rust docs we don't actually publish any documentation about the rust code in Qiskit as it's all explicitly internal. Or did you mean link to the rust language documentation (like: https://doc.rust-lang.org/book/)?

[jlapeyre]

There seems to be more than one convention on this, and sometimes non-plurals get s instead of '. Even so, none of the conventions I found favor class' over class's.

[sbrandhsn]

LGTM, I wonder whether we should include one "flashy" sentence along the lines of: Only the new major version (Qiskit 1.x series) will continue to receive performance improvements such as highlighted in (LINK) and new functionality that increases the productivity in working with quantum computers

[sbrandhsn]

I think one more sentence about backwards compatibility would be nice here: do we commit to only reading the output (e.g. quantum circuits) written by earlier Qiskit versions or do we commit to some API, i.e. guarantee that user code will run correctly for the entire lifecycle of a major release?

[mtreinish]

I'll come up with something. I was trying to avoid rehashing the entire contents of the documentation on this topic (which is what I ended up doing in my initial draft), but I definitely can see the value in explaining a bit more about what backwards compatibility means here.

[1ucian0]

I would remove the This page contains the release notes for Qiskit, starting from Qiskit 0.45, the first time that Qiskit and Qiskit Terra had the same versions. in docs/release_notes.rst:7

[jakelishman]

I've only read over the prelude of the release - I think we've already got enough people looking through everything else as well.

I agree with the top-level features that have been highlighted, and I couldn't think of anything else I'd want to promote up to those top-level bullets either.

[jakelishman]

Ok, assuming this passes the docs build, I think this is it for Qiskit 1.0.0.