1.9.6, 2.0 releng, schedule proposal

[Christian Stimming]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Josh Sled schrieb:
> 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
> 
>   - QSF Import [currently crashes on invocation :(]

IMHO all three should rather be hidden until we've got a clear positive
feedback about the current code and feature status.

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

*sigh* I'm not at all a postgresql user/developer, but if we remove/hide
this, it would be a feature regression compared to 1.8.x. I'd strongly
vote to keep it enabled, but #332251 certainly is a showstopper for that...

> 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.

Yes. Can you define "RC" a bit more clearly? Maybe write a short remark
about what that means into http://wiki.gnucash.org/wiki/Release_Schedule ?

> 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
>   [...]

Fine with me, except that I'd prefer to keep the "strictly increasing
numbering scheme" as Derek has already mentioned, i.e. call these
releases 1.9.7, 1.9.8, 1.9.9 etc.

Might mean that our pan atlantic gnucash developer party on June 11 in
NYC is much more of a 2.0.0 release party...

Christian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQCVAwUBRF7872XAi+BfhivFAQKhcgQAuqqKPDHouS5C4dEgplxsaBvBPp9Wh9PU
mlP1RzLiSKgh6jBJI7BNEAqULZSHhe4K8dF5ryuWxtiz+nGY8gqX/mVZD0xKD5Ud
gqm6nKfTpJyKXEhrQiOlwI69Vmz6O46Gr5Ou39cpX4VHoVrwSaW6jMKkKyxbQYn9
Ep2v/6ZSki4=
=4Je9
-----END PGP SIGNATURE-----