nano-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Nano-devel] GNU nano 2.3.4


From: Chris Allegretta
Subject: Re: [Nano-devel] GNU nano 2.3.4
Date: Wed, 9 Jul 2014 13:07:45 -0400

On 7/7/14, Benno Schulenberg <address@hidden> wrote:
>
> Hello Jordi,
>
> On Mon, Jul 7, 2014, at 10:26, Jordi Mallach wrote:
>> Ideally, I'd love to be in the position where I can chose between 2.2.7,
>> with all of the patches that have been collected in SVN and maybe fish
>> in all major repo distros to see if there's anything interesting, and
>> 2.4.x or at least 2.4.0rcX. Not sure if we'll be able to get to release
>> candidates during the summer, though.
>
> As far as I'm concerned, we can start the 2.3.99 dance by the end
> of this month or the beginning of August, and then have a 2.4.0
> in September.  Personally I have no interest in making a 2.2.7.

If you're interested in a 2.2.7 Jordi, I'm happy to backport anything
which applies cleanly while we dig into the late 2.3 cycle. I'd
probably want to focus on things which were already fixed earlier in
the 2.3 cycle which can go back relatively easily.  There have been
several larger changes which makes bringing back more recently fixed
bugs slightly more difficult.  If you can come up with a list of bugs
I'm happy to take a look this weekend, assuming my health holds up.

Making a release is very straightforward and automated though, and
we're definitely overdue for another 2.2 while we get 2.4 solidified.

> Chris, releasing a 2.3.5 as soon as you can would be nice.  Before

Happy to do so.

> going toward 2.4.0 there's some little thing in the undo/redo code
> that I'd like to see addressed, but all the other stuff that Mark
> is working on is so invasive that I don't feel comfortable putting
> it in now, it will have to wait for the 2.5.x branch (which we can
> start right after 2.4.0).

Sure.  I didn't have any huge features on the horizon and am very
interested in getting some remaining colorization bugs fixed, but that
could happen either in 2.3 or 2.5 with backports to 2.4.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]