[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150522194520.GA5918@openwall.com>
Date: Fri, 22 May 2015 22:45:20 +0300
From: Aleksey Cherepanov <lyosha@...nwall.com>
To: john-dev@...ts.openwall.com
Subject: Johnny: plan of releases
Shinnok, Mathieu,
According to Mathieu's proposal, there should be a release of johnny
with 1.4 and 1.5 soon. Summary of progress and current meeting on irc:
- We were slow defining 1.5.1 and 1.5.2 so Mathieu moved onto fixing
TODOs and basic Windows support, so 1.4 was enlarged,
- 1.5.1 is not started yet,
- 1.5.2 have multithreading, it causes minor problems because
processes go in parallel with user activities and may or may not give
expected results,
- Shinnok considered to not include 1.5 into the release,
- Shinnok would like to include his 1.2 and 1.3 into the release but
he may be not able to implement them due to his other tasks in the
beginning of June.
So it is unlikely that the release will be done in time.
We discussed that the deviation from proposal is not a problem for
Mathieu. I'd like to add: practical results should be delivered some
day. Preferably at least one stable release should be done before
midterm evaluation.
Rearrangements of releases does not seem a problem. But unclear plan
of releases seems a problem to me. So I'd like to see a clarification:
when the release is planned? What's included? What should Mathieu do
after implementation of code for release and before actual release?
(Current probable case: the release includes 1.2-1.4 and Mathieu works
on 1.5 and 1.6 when he finishes 1.4.)
But we don't know how much time the release will take. So it would be
safe to put 1 week onto testing, fixing bugs, packaging.
Thanks!
--
Regards,
Aleksey Cherepanov
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.
