Hi Otavio,
I understand the lack of a proper release cycle is an issue, but to solve
this I really need the help of the community. We've got a lot of people
doing an amazing job fixing bugs and backporting fixes to the stable-1.1
branch. The problem is that working on the release and fixing bugs
So would it be possible (assuming it is not already done) to define some roles
with responsibilities that need be filled? Then perhaps using that information
ask for volunteers? I would suggest defining these roles in a fashion that
would allow the community participants to commit to a
Hi Nik,
Thank you for your offer! Regarding your work on smartcard, I'm sorry I
didn't find the time to take a closer look at it, but please keep doing
what you're doing :)
As for avoiding asking someone to commit to a non-paying second job, that's
pretty much always been the issue for community
Hi Otavio,
as Marc-Andre already said we are short on time and man power.
Since the last release a lot of new features and clients where added,
the code base and functionality is growing.
One really big and hard problem we face is the complexity of RDP. It
ain't an easy job to test all
Hello Bernhard,
First I'd like to make clear it is not a criticism per si, but a
constructive critic.
On Tue, Oct 22, 2013 at 1:37 PM, Bernhard Miklautz
bmikla...@thinstuff.at wrote:
as Marc-Andre already said we are short on time and man power.
Since the last release a lot of new features and
Hi Otavio,
I understand that this is constructive criticism, the issue is mostly with
the fact that one cannot realistically do what you suggest. Freezing master
is not an option, which is why we've made a stabilization branch: the code
there is simply stabilized over time with no breaking
On Tue, Oct 22, 2013 at 2:34 PM, Marc-André Moreau
marcandre.mor...@gmail.com wrote:
I understand that this is constructive criticism, the issue is mostly with
the fact that one cannot realistically do what you suggest. Freezing master
is not an option, which is why we've made a stabilization
Hi Otavio,
You may not realize it, but the vast majority of the work I'm doing for
customers is upstream from the start, and this include bug fixes,
performance improvements, architectural fixes. The problem I think you have
is the features you care mostly about (serial, parallel, smartcard) are
Hi Otavio,
All of this being said, I actually do care about fixing serial, parallel
and smartcard. I'm quite happy to see Thinstuff's been putting some
resources on smartcard and serial recently, and that Nik who responded
earlier in this thread is now on IRC, ready to help. I think the most
Hello Marc-Andre,
On Tue, Oct 22, 2013 at 4:18 PM, Marc-André Moreau
marcandre.mor...@gmail.com wrote:
All of this being said, I actually do care about fixing serial, parallel and
smartcard. I'm quite happy to see Thinstuff's been putting some resources on
smartcard and serial recently, and
I would like to express my concern too over the stability of FreeRDP.
It was much better a year ago.
I'm concerned / confused about the future of FreeRDP.
It seems like there is too many restructuring / refactoring of the
source code that add no value.
All the documentation on
11 matches
Mail list logo
