by database integration do you mean persistence layer?..

On 02/11/05, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
> All,
>
>  As we just have release 1.1 I'd like to start a feature discussion on
> Wicket 1.2, and on what timeframe we wish to ship it.
>
>  What are our major concerns for Wicket 1.2?
>
>  I just list a few things I think could be on the feature list:
>
>   - reference documentation
>   - database integration
>   - session size/state management
>   - single component markup generation
>   - portal support
>   - testing
>
>  I also think we should aim for some release date. I would like us to focus
> on smaller releases, and maybe strive for 4 releases per year. Currently we
> are at 2.1 releases per year. My proposal is to do time-boxed, feature
> driven development, aiming for high quality and less focus on more features
> per release. Having a schedule of 4 releases, means releasing each 3 months.
> Currently a typical release candidate is out there for about 3 weeks, and we
> usually have 2 release candidates. This means the last 6 weeks are RC time.
> This is half of a 3 month release, and seems too much IMO.
>
>  Your thoughts please?
>
>  Martijn
>
> --
> Living a wicket life...
>
> Martijn Dashorst - http://www.jroller.com/page/dashorst
>
> Wicket 1.1 is out: http://wicket.sourceforge.net/wicket-1.1
HS^�隊X���'���u��jg����z�������!jY^���+a����z�'�j�������'���������y��m秵��v�0�v�ڙZ�f�������z���t��+f=#–'$��޶�ek(m������q����z��z�'�j)���rG�u�ޖ�fj)b�
   b�բrG�u�ޖ�e��l���q����z�m��?�X���(��~��zw��X������b��?�'$z�^�

Reply via email to