[Kst] Architectural changes

[Brisset, Nicolas]

> So:  From now to 2.0, we should work only on critical bug fixes and
> critical or very easy feature fixes, which a goal of a 2.0 release on
the
> weekend of January 1.
> 
> The exception to this would be if we find a reason we would need to do
an
> API change to data-sources or plugins, in which case the Jan 1 release
> would be called '2.0-beta4'
> 
> Thoughts?
For the technical part, I don't have any valuable opinion. I'll leave it
to more experienced developers to say what they think about it. As I
said before, I would have been interested to know what George's team
(who put lots of thought and effort into the port) are thinking, but
apparently they've moved on to something else now...

Apart from that, I think:
- that the target of January 1st is a bit optimistic if we want a really
smooth user experience. I am aware of a couple of bugs, which are not
yet all reported. According to available resources it could take a bit
of time to fix. Nothing looks really badly broken, so it may be
feasible. But there are still a couple of quirks around. In any case, I
welcome the idea of switching to bug-fixing and soft feature freeze if
the infrastructure is stable enough.
- that data sources (and possibly plugins, I haven't looked) have become
much more complex than they used to be and could use a bit of
documentation or API review. For instance the way config widgets and
loading/saving work is a bit confusing to me right now. I have looked
mainly at ASCII. I will try to detail my thoughts in a later post.

Nicolas 


Eurocopter Deutschland GmbH
Sitz der Gesellschaft/Registered Office: Donauwoerth
Registergericht/Registration Court: Amtsgericht Augsburg HRB 16508
Vorsitzender des Aufsichtsrates/Chairman of the Supervisory Board: Dr. Lutz Bertling
Geschaeftsfuehrung/Board of Management:
Dr. Wolfgang Schoder, Vorsitzender/CEO; Friedrich-Wilhelm Hormel; Ralf Barnscheidt

CONFIDENTIALITY NOTICE 

This communication and the information it contains is intended for the addressee(s) named above and for no other persons or organizations. It is confidential and may be legally privileged and protected by law. The unauthorized use, copying or disclosure of this communication or any part of it is prohibited and may be unlawful. 
If you have received this communication in error, kindly notify us by return e-mail and discard and/or delete the communication. Thank you very much. 
It is possible for e-mails to be intercepted or affected by viruses. Whilst we maintain virus checks on our e-mails, we accept no liability for viruses or other material which might be introduced with this message.