ZAP ... 2.0.0 !

[psiinon]

I know I've just posted about ZAP 1.4.1, but I also want us to start thinking about the next 'functional' release as well.

I think it should include the 3 GSoC projects, and ideally the restructuring to allow existing major extensions and all of the scanner rules to be updated without a new install, as per the other thread.

And I think thats enough to justify calling it 2.0.0 :)
Not sure when that will be - when we're happy with all of those changes I guess, and I havnt started on the restructuring code yet (but will do soon)!

Does that sound like a plan?
Is the move to 2.0.0 reasonable?

Any other major changes you would like to see in it?

Cheers,

Simon

[psiinon]

Guifre has just pointed out to me that Java 1.6 support ends in November 2012: http://www.oracle.com/technetwork/java/eol-135779.html
I dont like the idea of changing our requirements for 1.4.1 so I think 2.0.0 could be a good time for us to officially switch to 1.7.
That means we would no longer support 1.6, and can make full use of all of the 1.7 features.

Anyone disagree?

Simon

[Leandro Ferrari]

It seems perfect. then when we started to compile with java 1.7?

Leandro

[Axel Neumann]

I think that it would be ideal to switch to 1.7 with the release of ZAP 2.0. A question that arises because of such an upgrade is if the contained libraries are also compatible to this new Java version. Might be more work to switch to 1.7 than expected...

Cheers,

Axel

--
You received this message because you are subscribed to the Google Groups "zaproxy-develop" group.
To view this discussion on the web visit https://groups.google.com/d/msg/zaproxy-develop/-/78nP_iJMe-QJ.
To post to this group, send email to zaproxy...@googlegroups.com.
To unsubscribe from this group, send email to zaproxy-devel...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/zaproxy-develop?hl=en.

[psiinon]

@ Leandro - yes, if agreed then we'll switch to use java 1.7 on the trunk, but not on the 1.4 branch. I'll see if theres any more feedback and if not reply to this thread to say we should all switch.

@ Axel - I started using Java 1.7 and it seemed to work fine, so I'm hoping it will be a relatively painless switch over :)

Cheers,

Simon

On Friday, 27 July 2012 13:55:16 UTC+1, Axel Neumann wrote:

I think that it would be ideal to switch to 1.7 with the release of ZAP 2.0. A question that arises because of such an upgrade is if the contained libraries are also compatible to this new Java version. Might be more work to switch to 1.7 than expected...

Cheers,

Axel

On 27.07.2012, at 13:29, psiinon <psi...@gmail.com> wrote:

Guifre has just pointed out to me that Java 1.6 support ends in November 2012: http://www.oracle.com/technetwork/java/eol-135779.html
I dont like the idea of changing our requirements for 1.4.1 so I think 2.0.0 could be a good time for us to officially switch to 1.7.
That means we would no longer support 1.6, and can make full use of all of the 1.7 features.

Anyone disagree?

Simon

On Thursday, 26 July 2012 14:28:21 UTC+1, psiinon wrote:

I know I've just posted about ZAP 1.4.1, but I also want us to start thinking about the next 'functional' release as well.

I think it should include the 3 GSoC projects, and ideally the restructuring to allow existing major extensions and all of the scanner rules to be updated without a new install, as per the other thread.

And I think thats enough to justify calling it 2.0.0 :)
Not sure when that will be - when we're happy with all of those changes I guess, and I havnt started on the restructuring code yet (but will do soon)!

Does that sound like a plan?
Is the move to 2.0.0 reasonable?

Any other major changes you would like to see in it?

Cheers,

Simon

--
You received this message because you are subscribed to the Google Groups "zaproxy-develop" group.
To view this discussion on the web visit https://groups.google.com/d/msg/zaproxy-develop/-/78nP_iJMe-QJ.

To post to this group, send email to zaproxy-develop@googlegroups.com.
To unsubscribe from this group, send email to zaproxy-develop+unsubscribe@googlegroups.com.

[Guifre Ruiz Utges]

Hello,

Just for the record, Oracle just extended (again) the support of Java 6 to February 2013.

https://blogs.oracle.com/henrik/entry/java_6_eol_h_h

Best regards.

[Raul Siles]

Guifre,
Most probably they did because they were monitoring this mailing-list
thread and were worried about ZAP 2.0 switching to Java 1.7 ;-D
Seriously, I agree 2.0 is the right time to switch.

Anyone interested on contributing support for new smartcards so that
we can add them by default on ZAP version 2.0?
https://code.google.com/p/zaproxy/wiki/SmartCards

Please, feel free to contact me if any help is needed.
--
Raul Siles - www.raulsiles.com
Founder & Senior Security Analyst
Taddong (www.taddong.com)

> --
> You received this message because you are subscribed to the Google Groups
> "zaproxy-develop" group.
> To view this discussion on the web visit

> https://groups.google.com/d/msg/zaproxy-develop/-/eALMRJRgDuYJ.
>
> To post to this group, send email to zaproxy...@googlegroups.com.

> To unsubscribe from this group, send email to

> zaproxy-devel...@googlegroups.com.

[psiinon]

I've updated the 'Roadmap' tab on the home page with some details about 2.0.0 (https://www.owasp.org/index.php/OWASP_Zed_Attack_Proxy_Project#Roadmap)

I've given a provisional date as sometime in autumn 2012.
Thats because there are a load more things I'd like to get in ;)
As we get into September we should start thinking about exactly what is feasible to release - I want to make sure we get all the great features already implemented out there sooner rather than later.

Let me know if you have any feedback...

Many thanks,

Simon

On Thursday, 26 July 2012 14:28:21 UTC+1, psiinon wrote:

[psiinon]

And I've also just updated the Credits in the trunk to split out the current 'core team' : https://code.google.com/p/zaproxy/source/browse/trunk/src/help/zaphelp/zaphelp/credits.html
Note that the 'current release' referred to in that file hasnt actually happened yet - so this is for post 1.4.1 work, ie things that will be in 2.0.0!
And as 2.0.0 is not imminent, theres time to get more changes in ;)

Please let me know asap if you are not correctly credited - whether you're missing, in the wrong section, wrong name or company etc etc.

Many thanks,

Simon

[psiinon]

After prompting from Colm I've just created a 1.4 branch in the zap-extensions project.

So extensions in the trunk can now use 2.0 features.
Note that the downloads should be generated from the 1.4 branch - if you want to use any 2.0 specific ones then for now you should build them yourself.

And this seems like a good time to switch to Java 7 on the trunk(s), especially since Java 7 has now been patched ;)

So please carry on using Java 6 on the zaproxy and zap-extensions 1.4 branches, but feel free to use Java 7 on the trunks.

Many thanks,

Simon