Re: Build System

Niklas Andersson <[email protected]>
Newsgroups gmane.comp.gnome.gaim.devel
Message-ID <[email protected]>
Hi Gary,

  I guess we have a couple of hundred users on Pidgin 3 and there are no 
other complaints than the notification system is pretty much broken in 
3.0 on Ubuntu. Besides that Pidgin 3 works pretty darn well for our users.


But I guess we might be a corner case here. I know that lots of users in 
other companies are just using 2.x.y as you say.

Would you know if the 3.0 release blockers are cleaned up? Is there a 
authoritative list I perhaps could point some of our developers to and 
have a look and see if they can contribute with something?

Regards,

Niklas

On 19/08/16 20:25, Gary Kramlich wrote:
> On Thu, Aug 18, 2016 at 11:19 AM, Niklas Andersson
> <[email protected]> wrote:
>> Would this speed up the release of Pidgin 3 in any way?
> No, the only thing that's going to get Pidgin 3 out faster is more
> people fixing all of the rough edges.  I've been systematically going
> through the code base and cleaning up every single thing I can.  I
> have 2 pull requests that still need more reviews, and I have 4 more
> that I'm working on right now.  Al of that and I haven't even tried to
> tackle some of the bugs I keep hitting.
>
> I think the biggest problem is that people are not dog fooding Pidgin.
> It's easy to just use the 2.x.y release and forget about 3.0.
> However, I use 3.0 every day, and I can't even tackle the bugs I'm
> finding because of other problems that are buried in the library.
>
> Long story short, we need to move faster, need more cooks, and of
> course, more hours in a day.
>
>> - Niklas
> Thanks,
>
> --
> Gary Kramlich <[email protected]>

_______________________________________________
Devel mailing list
[email protected]
https://pidgin.im/cgi-bin/mailman/listinfo/devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.