You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by Thomas Vandahl <tv...@apache.org> on 2010/04/19 20:53:04 UTC

[VOTE Result] Release fulcrum-cache-1.1.0 based on RC1

On 31.03.10 15:52, Thomas Vandahl wrote:
> A release candidate for fulcrum-cache-1.1.0 has been prepared.
> Please verify this release candidate and vote...

Vote results:

We have three binding +1 votes

- Siegfried Goeschl
- Thomas Vandahl
- Jürgen Hoffmann

No 0 and -1 votes were cast. The vote has passed. Thanks to all the voters.

Bye, Thomas.



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org


Re: [VOTE Result] Release fulcrum-cache-1.1.0 based on RC1

Posted by Siegfried Goeschl <si...@it20one.at>.
Hi Thomas,

see my comments below ...

Siegfried Goeschl

On 19.04.10 21:30, Thomas Vandahl wrote:
> Hi Siegfried,
>
> On 19.04.10 21:11, Thomas Vandahl wrote:
>> On 19.04.10 21:06, Siegfried Goeschl wrote:
>>> what else is missing for cutting Turbine 4.0?
>>
>> Hopefully not much. I need to check. There are some Turbine Services
>> that would need to be ported or just copied over from 2.3.3 (with my
>> current preference being the latter), such as UIService and JSON-RPC.
>> Volunteers are welcome.
>
> Ok. I suggest to do a milestone release like 4.0-M1 to see how it goes.
>> From my quick look through the code I see the following open points:
>
> - Currently, there is no implementation of the scheduler service.
> Turbine provides scheduled jobs as a module type of its own. How would
> something like this work with Quartz? If you could help me with this, I
> would be eternally grateful.

I will have a look but please note that "eternally" seems pretty long 
... ;-)

>
> - The security service is next to non-existent. I suggest to copy the
> current versions of the LDAP- and the Torque security service over from
> 2.3.3 for this milestone. I will try to get some Fulcrum security
> releases out rsn to be included in Milestone 2.

ok

>
> - I proposed a TurbineServiceProvider implementation based on OSGi
> (Apache Felix). Should that be included in the current milestone?
>

+0

> - The Maven2-Build needs to be checked and streamlined. Shall we use the
> fulcrum-parent POM for Turbine as well?

I will have another look ...

>
> Comments of *everybody* are very welcome.
>
> Bye, Thomas
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
> For additional commands, e-mail: dev-help@turbine.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org


Re: [VOTE Result] Release fulcrum-cache-1.1.0 based on RC1

Posted by Thomas Vandahl <tv...@apache.org>.
Hi Siegfried,

On 19.04.10 21:11, Thomas Vandahl wrote:
> On 19.04.10 21:06, Siegfried Goeschl wrote:
>> what else is missing for cutting Turbine 4.0?
> 
> Hopefully not much. I need to check. There are some Turbine Services
> that would need to be ported or just copied over from 2.3.3 (with my
> current preference being the latter), such as UIService and JSON-RPC.
> Volunteers are welcome.

Ok. I suggest to do a milestone release like 4.0-M1 to see how it goes.
>From my quick look through the code I see the following open points:

- Currently, there is no implementation of the scheduler service.
Turbine provides scheduled jobs as a module type of its own. How would
something like this work with Quartz? If you could help me with this, I
would be eternally grateful.

- The security service is next to non-existent. I suggest to copy the
current versions of the LDAP- and the Torque security service over from
2.3.3 for this milestone. I will try to get some Fulcrum security
releases out rsn to be included in Milestone 2.

- I proposed a TurbineServiceProvider implementation based on OSGi
(Apache Felix). Should that be included in the current milestone?

- The Maven2-Build needs to be checked and streamlined. Shall we use the
fulcrum-parent POM for Turbine as well?

Comments of *everybody* are very welcome.

Bye, Thomas

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org


Re: [VOTE Result] Release fulcrum-cache-1.1.0 based on RC1

Posted by Thomas Vandahl <tv...@apache.org>.
On 19.04.10 21:06, Siegfried Goeschl wrote:
> what else is missing for cutting Turbine 4.0?

Hopefully not much. I need to check. There are some Turbine Services
that would need to be ported or just copied over from 2.3.3 (with my
current preference being the latter), such as UIService and JSON-RPC.
Volunteers are welcome.

Bye, Thomas.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org


Re: [VOTE Result] Release fulcrum-cache-1.1.0 based on RC1

Posted by Siegfried Goeschl <si...@it20one.at>.
Hi Thomas,

what else is missing for cutting Turbine 4.0?

Cheers,

Siegfried Goeschl

On 19.04.10 20:53, Thomas Vandahl wrote:
> On 31.03.10 15:52, Thomas Vandahl wrote:
>> A release candidate for fulcrum-cache-1.1.0 has been prepared.
>> Please verify this release candidate and vote...
>
> Vote results:
>
> We have three binding +1 votes
>
> - Siegfried Goeschl
> - Thomas Vandahl
> - Jürgen Hoffmann
>
> No 0 and -1 votes were cast. The vote has passed. Thanks to all the voters.
>
> Bye, Thomas.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
> For additional commands, e-mail: dev-help@turbine.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org