Thanks.
On Tue, Mar 4, 2008 at 9:51 PM, Thorsten Haude <[EMAIL PROTECTED]> wrote:
> 1. Determine release-critical bugs
> Meaning we should all huddle and create a list of things that have to
> be fixed before RC1. This would include stuff from the SF tracker but
> also anything else we could come up with.
>
> The situation in the bug tracker is really beyond silly. Eddy wrote in
> his mail kicking off the 5.4 release: "The list of open bugs at SF is
> getting far too long." We had around 70 entries then, we now have more
> than a hundred.
>
> When we have a list we can agree on, we enter the bugs into the SF
> tracker (most should already be in) with a priority of 9.
>
> Bugs introduced after the last release should get special consideration.
Here is my list, which should be committed/considered/discussed:
1. smartIndent.c: remove static
I posted it here:
http://www.nedit.org/pipermail/develop/2008-January/014028.html
and Steve commented on this here:
http://www.nedit.org/pipermail/develop/2008-March/014173.html
2. #1894726 fix memory leak in PromoteToGlobal()
3. #1888195 calltip's ID not returned correctly
I haven't tested this throughly yet, but I will.
And maybe my follow-up patch from patch #1633136, which shows only
the 'not fount'-
calltip from the menu action, but not from the calltip()-macro
4. #1907176 Empty $file_path
just posted
5. #1869948 {forward,backward}_paragraph() broken with multi blank lines
this isn't really release critical, but the problem is real and
the patch is simple (if
you remove most of the small style changes)
>
>
> 2. Fix bugs
> There are currently two release-critical bugs left:
>
> #1600102 Add example .nedit to release tarball
> This is a pseudo-bug, as nothing is really wrong here. The work is
> largely done, the result should be checked by others though.
>
> #1027807 loss of files on full disk
> A solution is discussed. A patch limiting the damage is already there,
> a better solution does not look so hard.
#1869862 "^" doesn't match all lines
Has a patch, but can someone confirm its correctness!
>
>
> 3. Settings transition (updatePatternsTo5dot6() etc.)
>
> Any volunteers?
I thought this was done?
Do we need pre-built binaries at the time the source release is made?
Bert
>
>
> Thorsten
--
NEdit Develop mailing list - [email protected]
http://www.nedit.org/mailman/listinfo/develop
