Hi,
I was not able to attend the meeting yesterday thus I want to express
my opinion about providing builds to general public.
I think we should start providing regular development snapshots from
aquavcl01. I already did, because it is only about one more rsync
call for me. I'd be glad if someone wants to take over this mini task
from me.
When we have steady stream of new builds, users who are interested
can test them regularly. And we could announce this (because I feel
that Eric just wants to announce something...)!
We should work on integration of aquafilepicker01 to the master and
then resync aquavcl01 into the milestone with it. After this step,
our "regular development snapshot" automatically contains native
filepicker automatically and we can prevent doing non-repeatable
hacks like integrating several CWSes together...
I strongly disagree with providing patched builds to general public.
We should provide what we have. If the patches are not inside CWS,
they are not GOOD enough. We do not want to provide something which
is not GOOD enough to users! Fix the patches, prepare them for cws!
When they are there, they will be included in the next development
snapshot automatically!
From the meeting log, I see that many people "just want to get
something out". This is not how we worked in the past and I do not
follow the reasoning for this. Please do it properly directly from
the beginning!
In the meantime, we should work on some documentation for our users,
like:
- README first
- list of KNOWN BUGS
- how and where to repeat new bugs
Preparing this properly will be a big benefit for us when we want to
make some development snapshot an "alpha".
--
Pavel Janík
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
