Roadmap OSCAR 1.1

[fingolfin]

We recently had some discussion about when to make an OSCAR 1.1 release.

The rules are that in this release all book examples must still work, but unlike the 1.0.x releases, some printing relevant for the book may change.

We probably want such a release before the Begehung so that referees see us at our best when they install OSCAR the regular way (i.e. a non-dev release version). Software demos are still free to showcase unreleased features.

The other motivation for having a 1.1 release is so that our tutorials on the website can make use of new features.

However, when we talked about it laste Friday and Wednesday, there was some disagreement on whether we should release this soon, and be willing to have, say another release 1.2 for the Begehung; or whether to delay this as much as possible.

I am opening this issue now (with a week delay, sorry!!!) so we can discuss this further and come to a resolution.

In particular, we should answer this:

1. Do we make a 1.1 release before the Begehung?
   • (if there are things you believe must be dealt with before such a release, feel free to point them out in comments, too)
2. If yes to 1: Do we make this "soon" (say before the end of May), or do we delay to be really close before the Begehung?
3. If "soon" to 2: OK to make another release (possibly 1.2) just before the Begehung (assuming there is need for it, of course)?

My stance is "yes, soon, yes". I quite frankly did not understand the counter arguments to this made on Friday (e.g. it was claimed that having a 1.1 release would make it appear as if OSCAR was full of bugs and we already need fix releases now. Counterpoint: if this is a concern, then we should quickly get rid of the 1.0.1 and 1.0.2 releases..). Moreover, I'd say this actually looks as if we are very active in adding new features, esp. if we have a proper changelog / news item somewhere that explains this?

But of course I may have misunderstood, so I'll wait for others to explain their concerns