[Padre-dev] blocker for next release: padre preferences, settings, etc not saved / restored

[Adam Kennedy]

Yep, apologies for this.

Once I get the last of this stuff in, the structure of the internals
looks pretty good and should put us in a position to stay largely
stable for a good couple of months.

Adam K

2009/1/16 Gabor Szabo <szabgab at gmail.com>:
> I don't mind delaying the release even by 2 weeks - I won't be around anyway
> between 22/2 1/3 - if it means that after that we can have some stability
> for a month or two.
>
> I personally had to stop using trunk as I was busy with $work and did
> not have time
> to track down all the small and big issues encountered in trunk.
>
> I think some of the others had also pulled back a bit from development as
> things are too fragile.
>
> Gabor
>
>
> On Fri, Jan 16, 2009 at 4:51 AM, Adam Kennedy
> <adamkennedybackup at gmail.com> wrote:
>> I absolutely want to get the configuration changes in before the next release.
>>
>> Part of that involves getting the stuff that's actually host-specific
>> history data out of the user-specific configuration, which is what's
>> led me off Yak shaving on the ORLite auto-documentation.
>>
>> I'm happy to skip a release weekend and target next weekend, if it
>> gets all the breakages into a single release.
>>
>> Anyone else mind a one week release gap?
>>
>> Adam K
>>
>> 2009/1/16 Jerome Quelin <jquelin at gmail.com>:
>>> hi,
>>>
>>> bug 228 is a blocker for next release from my point of view: padre
>>> doesn't store or restore any preference.
>>>
>>> happens with 0.25 official and up-to-date svn snapshot.
>>>
>>> jérôme
>>> --
>>> jquelin at gmail.com
> _______________________________________________
> Padre-dev mailing list
> Padre-dev at perlide.org
> http://mail.perlide.org/mailman/listinfo/padre-dev
>