One critical security flaw...
salinasv at gmail.com
Sun Jan 31 16:41:35 EST 2010
On Sun, Jan 31, 2010 at 3:12 PM, John Bailey <rekkanoryo at rekkanoryo.org> wrote:
> On 01/13/2010 11:27 PM, John Bailey wrote:
>> My only reason for being hesitant to rush to 3.0.0 is that I was hoping we could
>> get gobjectification done for 3.0.0, but I don't see that happening. In the
>> interests of Getting Stuff Done(TM), I propose the following:
>> * Finish the ICQ X-Status stuff ASAP for 2.7.0 (string freeze
>> for release within 3 days of completed merge).
>> * As soon as 2.7.0 is out, create a branch such as
>> im.pidgin.pidgin.2.7.x (I'm open to better names) from the tag
>> of 2.7.0 for future maintenance releases.
>> * Once 2.7.x is branched, 2.x.y is API frozen--no new API unless
>> absolutely required to fix a security issue.
>> * Once 2.7.x is branched, im.pidgin.pidgin is for 3.0.0 development.
>> All new features, API additions, etc. should happen only on this
>> branch or other branches that will be merged *only* to
>> Thoughts, better ideas, etc are certainly welcome.
> No one has bothered to reply to this message in the last two and a half weeks.
> Should I assume this means no one wants to do any of this?
I think it's a great idea but I think it would be nice to have some
TODO list and the factibility(?) of each point.
AFAIK it was planned to have working
Merge keyring stuff
Stop doing blockong IO
Merge privacy rewrite (it's it complete?)
I would like to get smiley themes and adium themes merged as theme loader
On gobjectifications: What about release 2.7.0 and then feature freeze
for some weeks so it gobjectification people can get a non-moving
target and get it done, then start 3.0.0 movement over gobjectificated
Do you have some expected time to get 3.0.0 done?
More information about the Devel