[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20121210000905.GD4421@openwall.com>
Date: Mon, 10 Dec 2012 04:09:05 +0400
From: Solar Designer <solar@...nwall.com>
To: john-dev@...ts.openwall.com
Subject: Re: self-test duration vs. GPU benchmarks
On Sun, Dec 09, 2012 at 04:27:26AM +0100, magnum wrote:
> The only thing I merged was the tiny self-test patch. It does not change any interface.
Oh, that's fine.
> On 9 Dec, 2012, at 2:40 , Solar Designer <solar@...nwall.com> wrote:
> > As to my plans for releasing a new core version, this should happen no
> > later than April 2013.
>
> That is ages from now, but OK.
"No later than" does not mean it won't happen sooner, although it will
definitely not happen in December or January, unfortunately. So this
leaves us Feb through Apr as the possible range for the 1.8 release.
> Do we need to release a J8 at all? Just before a core release - which is then followed by a J1? I'm not so sure.
I'm not sure either, but it does make sense to me to separate the many
changes that have been accumulated in jumbo from the core changes in 1.8,
so a 1.7.9-J8 release makes sense to me even if just for "revision
control" (yes, we use git, but releases tend to be a bit more stabilized).
> The bottom line is I would like to merge all your patches to bleeding, but I just can't do that and still maintain a tree without them. After the jumbo-6-fixes experience I am absolutely sure it will end up a mess. We need to have *one* tree for people like Dhiru or Claudio to commit to. If that is bleeding, someone need to backport patches. If it's unstable, someone need to forward-port them. I do not wish to do either, I want to write formats.
I am fine with you actively working on just one tree, and it can be the
one that we'll release after 1.8. In that case, though, we should
expect that 1.7.9-J8, if released, will _not_ include much of the new
stuff. So e.g. some of Dhiru's edits to the wiki promising certain
things in -J8 specifically may be wrong and will need to be adjusted (no
problem, we can do that).
Alexander
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
