1.9.6, 2.0 releng, schedule proposal

[Josh Sled]

Call for help: If 1.9.6 is going to go out tonight, there are still two
failing tests (test-query and test-period) to resolve.


For 2.0, as well, there's still a lot left.  In particular...

http://bugzilla.gnome.org/buglist.cgi?product=GnuCash&bug_status=NEW&bug_status=REOPENED&bug_status=ASSIGNED&bug_status=UNCONFIRMED&target_milestone=2.0.0

...is the 2.0-blocker list.  It still has two unconfirmed critical bugs
that we should get some eyes on...

As well, there's a critical SX bug that I discovered yesterday, and a
normal that Tim Wunder encountered that's already been fixed (and
another that I'm unable to confirm).  In any case, there's still a lot
of codebase volatility...


Plus, we still need to reach decisions regarding removing or hiding:

  - Lots
    - sounds like "no", though we should hide the "View" button in
      the editor.

  - Close Books

  - PostGres support
    - configure.in/building support
    - Open/Save (more of a "don't do anything else"; Bug#332251).

  - QSF Import [currently crashes on invocation :(]


Even if 1.9.6 goes out today, we need at least one more release, and
should do at least one RC; as such, having 2.0.0 next Sunday (May 14) is
impossible.

[Actually, I only now realize that
http://wiki.gnucash.org/wiki/Release_Schedule was updated to have 2.0.0.
on May 21st... even that seems unlikely, right now.]


I propose the following schedule:

- 1.9.6 release today/tomorrow/Tue... (ultimately it'll be decided by 
  the tests passing).

- Weekly RC's until release, thus...
  - 2.0.0-rc1 on 14 May
  - 2.0.0-rc2 (or 2.0.0) on 21 May
  - 2.0.0-rc3 (or 2.0.0) on 28 May
  [...]

-- 
...jsled
http://asynchronous.org/ - `a=jsled; b=asynchronous.org; echo ${a}@${b}`