-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Aloha!
Really good with the release plan page for Nettle: http://www.lysator.liu.se/~nisse/nettle/plan.html
A few (bikeshed) comments etc.
(1) I would suggest not using colors as distinguisher for what is done (green), what is critical for the release (red) and what is nice to have (grayish). I would instead suggest having subsections with explicit headers stating this instead (done, important, nice to have). Colors are harder to parse and esp red-green is bad when dealing with a lot of male individuals.
(2) How about putting up an estimated release schedule at the top of the page. For example such as:
- - 2014-01-xx: Feature freeze for 2.8 (branch date) - - 2014-02-xx: Testing and bug fix completed. - - 2014-03-xx: 2.8 RC1 - - 2014-04-xx: 2.8 Released (label date)
(I have no idea what release schedule you in fact have in mind - if it is 4 days, 4 weeks of 4 months to do the release.)
(3) I'll try and work on the chacha support files the next weeks.
(4) I'm prepared to do the darwin testing on OSX 10.9.x
- -- Med vänlig hälsning, Yours
Joachim Strömbergson - Alltid i harmonisk svängning. ======================================================================== Joachim Strömbergson Secworks AB joachim@secworks.se ========================================================================
Joachim Strömbergson joachim@secworks.se writes:
(1) I would suggest not using colors as distinguisher for what is done (green), what is critical for the release (red) and what is nice to have (grayish).
Feel free to play with the style sheet, it's the files misc/plan.html and misc/todo.css in the repo. One could use other colors, or both color and font style changes, or have several alternative stylesheets.
But I like the current organization, where I just switch the class of a paragraph to change the status, and it's also possible to change the status of just parts of a point using, e.g., <span class='done'>.
(2) How about putting up an estimated release schedule at the top of the page.
I'm afraid there's no schedule. Currently, this is a spare time project for me. Funding for full time work (even for just a few weeks) would help.
And then depending on how the memxor bug Nikos reported plays out (I'm looking into improving the test using VALGRIND_MAKE_MEM_NOACCESS client requests), it may be necessary to also do a 2.7.2 bugfix release in between.
(3) I'll try and work on the chacha support files the next weeks.
(4) I'm prepared to do the darwin testing on OSX 10.9.x
Good!
Regards, /Niels
nettle-bugs@lists.lysator.liu.se
-
Joachim Strömbergson -
nisse＠lysator.liu.se