2.0.0 unfinished feature deactivation (was:1.9.6, 2.0 releng, schedule proposal)

Christian Stimming stimming at tuhh.de
Fri May 19 11:05:01 EDT 2006


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

>> Josh Sled wrote:
>>> 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.
> 
> I agree.

I guess we should now start to actually hide/deactivate these three
features. I'd suggest to remove any menu item, toolbar button or other
button that reaches these features, and then record the location and SVN
revision of that deactivation in bugzilla target 2.0.x.

>>>   - 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...
> 
> I could probably fix #332251, but look at #313696.  The only reason to
> do anything with pg right now, IMO, would be to allow the immediate
> export to xml, but that's been impossible at least as far back as
> 1.8.11.  So, IMO, there's no point in fixing #332251 unless we're
> committed to fixing #313696 as well, and I have no idea how difficult
> that would be.  :(

Since there hasn't been any visible development in that area, I guess we
have to deactivate this for 2.0.0 as well. In that case unfortunately we
need to note this prominently in the release notes ("PostgreSQL support
is unfortunately disabled in 2.0.0 due to lack of sql developers, but is
a high priority to be working again in a later 2.x release.") So this
needs to be disabled as well, maybe with some error messages that says
exactly this.

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

iQCVAwUBRG3enWXAi+BfhivFAQIeDQP/dIetBjzqA/GxmCOEP3TCrC3SzqpgSpEy
Z9cV8TRTW284U/nTBHxNnxyH0vsGc1leDcSnvB2zLu1y3myjgtsHCbWhAm/CgbnL
yc0OYQYC4GfSsDhgCB76QfP5TBpLoZCMJg+X2B/qV+AURvjasiJQSfyrsOwxXBqz
WKGPyMhkhI0=
=JrE5
-----END PGP SIGNATURE-----


More information about the gnucash-devel mailing list