On Mon, Nov 4, 2013 at 5:01 PM, Bruno Oliveira <bruno@abstractj.org> wrote:

Good morning all, to make sure that we are all on the same page.

We have a lot of technical discussions a month ago about crypto and was
possible to learn together a ton of things, but of course the learning
curve is not dead simple. Initially the security release was scheduled
to 13th Nov with the freezing 1 week before (for testing and possible
bug hunting), after our meeting today
(http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2013/aerogear.2013-11-04-14.55.html)
our conclusion was that we might face some delays.

Targeting mid November I already reduced our scope and sent the roadmap
to the mailing list on the last week
(http://staging.aerogear.org/docs/planning/roadmaps/AeroGearSecurity/)
and today most of the Jiras were updated
(https://issues.jboss.org/issues/?jql=fixVersion%20%3D%20%221.3.0%22%20AND%20project%20%3D%20AGSEC%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC).
That said my suggestion is to change the dates:

- 13th Nov: Freezing
- 20th Nov: Encrypted storage release

What do you think?

I am fine w/ it - I guess this does effect the 'umbrella' release a bit as well;

Why not generally have this plan for all the parts, "freeze" on 13th - release the bits on 20th ?

-Matthias

If the scope is not sane and too much, please suggest
a better scope, If some detail is missing you should raise your hand and
if the dates are not ok, suggest.

--
abstractj

_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev

--
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf