Next Release = 1.103?

General Discussion
1

I was chatting briefly with @matterhorn103 and I think the next release really should be a 1.103 if we want to do it on 06-Feb. (It will mostly be a “2.0 prelease” anyway.)

  1. There have been a bunch of fairly major changes since 1.102, including use of OpenGL 4.0 and it would be great to get more bug testing. (Most users grab releases not continual builds.)
  2. Checking repology it seems like many Linux distros haven’t updated to 1.102 yet, likely because of the new plotting library (e.g., Debian and Ubuntu need to create JKQtPlotter packages before updating Avogadro).
  3. There’s still some work to finish up the new plugin pieces.
  4. We probably want to give translators more time to update new strings

And of course we’d want to make 2.0 as clean and bug-free as possible.

That’s not to say that 2.0 won’t be released until June. My thought is to make the 1.103 release on 06-Feb, and then fixup bugs for a 2.0 release in .. March or April. (Maybe April 1st? :slight_smile: )

Thoughts?

2

On a related note, I can think of two more features that could be merged for a 1.103 .. or saved for a summer 2.1 release (i.e., they’re basically done, but need more testing):

1 Like
3

Maybe an April 1st 2.0 release wouldn’t be the worst thing (also, hilarious to release on April 1st of all days). It’d also give time for the plugin framework to get finalized, which is something I think is pretty critical.

4

@brockdyer03 So you prefer e.g., March 14 (Albert Einstein’s birthday .and. pi day) / October 23 (mole day) with the advantage their reading is less likely to be misinterpreted depending how you express dates in the Gregorian calendar than say Amedeo Avogadro’s date of birth / day of death?

5

No no, I genuinely think it’d be funny to make an April 1st release of 2.0.

1 Like