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 2015/07/19 21:41:13 UTC
[VOTE] Release fulcrum-security 1.1.0 based on staged repository
Hi folks,
A release candidate for the Fulcrum Security Components, version 1.1.0
has been prepared. Please verify this release candidate
carefully and vote, vote, vote...
Tag:
https://svn.apache.org/repos/asf/turbine/fulcrum/tags/fulcrum-security-1.1.0
Artifacts:
https://repository.apache.org/content/repositories/orgapacheturbine-1007
[ ] +1 release it
[ ] +0 go ahead I don't care
[ ] -1 no, do not release it because
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
Re: [VOTE] Release fulcrum-security 1.1.0 based on staged repository
Posted by Siegfried Goeschl <sg...@gmx.at>.
Hi folks,
+1
Cheers,
Siegfried Goeschl
> On 19 Jul 2015, at 21:41, Thomas Vandahl <tv...@apache.org> wrote:
>
> Hi folks,
>
> A release candidate for the Fulcrum Security Components, version 1.1.0
> has been prepared. Please verify this release candidate
> carefully and vote, vote, vote...
>
> Tag:
>
> https://svn.apache.org/repos/asf/turbine/fulcrum/tags/fulcrum-security-1.1.0
>
> Artifacts:
>
> https://repository.apache.org/content/repositories/orgapacheturbine-1007
>
> [ ] +1 release it
> [ ] +0 go ahead I don't care
> [ ] -1 no, do not release it because
>
> Bye, Thomas.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
[RESULT][VOTE] Release fulcrum-security 1.1.0 based on staged repository
Posted by Thomas Vandahl <tv...@apache.org>.
On 19.07.15 21:41, Thomas Vandahl wrote:
> Hi folks,
>
> A release candidate for the Fulcrum Security Components, version 1.1.0
> has been prepared. Please verify this release candidate
> carefully and vote, vote, vote...
>
> Tag:
>
> https://svn.apache.org/repos/asf/turbine/fulcrum/tags/fulcrum-security-1.1.0
>
> Artifacts:
>
> https://repository.apache.org/content/repositories/orgapacheturbine-1007
Hi folks,
we have four binding +1 votes for the release candidate (in order of
appearance)
- Georg Kallidis
- Siegfried Goeschl
- Jürgen Hoffmann
- Thomas Vandahl
No 0 and -1 votes were cast. The vote has passed. I will be publishing
the artifacts on Nexus shortly. 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
Antwort: [VOTE] Release fulcrum-security 1.1.0 based on staged repository
Posted by Georg Kallidis <gk...@cedis.fu-berlin.de>.
Hi Thomas,
[x] +1 release it
[ ] +0 go ahead I don't care
[ ] -1 no, do not release it because
Best regards, Georg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
Re: [VOTE] Release fulcrum-security 1.1.0 based on staged repository
Posted by Jürgen Hoffmann <ho...@ellumination.de>.
Hi Folks,
> On 19.07.2015, at 21:41, Thomas Vandahl <tv...@apache.org> wrote:
>
>
> [X] +1 release it
> [ ] +0 go ahead I don't care
> [ ] -1 no, do not release it because
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
Re: [VOTE] Release fulcrum-security 1.1.0 based on staged repository
Posted by Thomas Vandahl <tv...@apache.org>.
On 19.07.15 21:41, Thomas Vandahl wrote:
> [X] +1 release it
> [ ] +0 go ahead I don't care
> [ ] -1 no, do not release it because
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
Re: Antwort: Re: Antwort: Re: Turbine 4.0 M2 Archetype Trunk Release
Posted by Siegfried Goeschl <si...@it20one.com>.
Hi folks,
@ApacheCon - since I’m on a new project with a couple of deadlines I won’t be there :-(
Sigi
> On 28 Jul 2015, at 16:37, Georg Kallidis <gk...@cedis.fu-berlin.de> wrote:
>
> Hi Thomas,
>
> I think it is ok to remove or deprecate TorqueSchedulerService and remove
> SQL script generation. If you have a lot of jobs may be it´s useful, but
> more appropriate in Fulcrum Quartz or better Fulcrum Security, because of
> the dependencies and it´s a kind of security question having scheduled
> jobs configuration in a database, isn´t it? ;-).
>
> BTW: In Fulcrum Security the Opensymphony and Turbine Adapters seem to be
> deprecated or otherwise removable.
>
> @4.0FinalRelease
> I think it would be not a bad idea to set an release date target, e.g. in
> December or January for 4.0 final, if it´s only about internal stuff. Then
> we could focus, what is really needed, (doing some more cleanup?) ...
>
> @ApacheCon: I should definitely decide it this week (coming to Apache
> Core). You could make it? Siegfried as well?
>
> Best regards, Georg
>
>
>
>
>
> Von: Thomas Vandahl <tv...@apache.org>
> An: Turbine Developers List <de...@turbine.apache.org>
> Datum: 27.07.2015 19:43
> Betreff: Re: Antwort: Re: Turbine 4.0 M2 Archetype Trunk Release
>
>
>
> Hi Georg,
>
> On 27.07.15 17:19, Georg Kallidis wrote:
>> wow, it seems you updated the scheduler already! Tests are running
>> successfully here (Windows, Java 1.7).
>
> Good to know. I guess some docs are still missing.
> Do we want to deprecate the TorqueSchedulerService now? If so, I could
> remove the whole SQL script generation stuff from the POM and make
> Torque an optional dependency. WDYT?
>
>> Do you think Turbine M2 release is ready for take-off (in September or
>> earlier)? ;-) We could release the archetype build then soon after this.
>
>
> Yes, if it's a milestone release. I would like to clean up the module
> stuff and RunData/PipelineData mess before going 4.0 final.
>
>> P.S: More upcoming releases are Fulcrum Testcontainer and Yaafi
> hopefully.
>> Wasn´t a new Fulcrum Script in discussion, of course without backporting
>
>> to Java 8 Nashorn (as far as I know ;-) ..
>
> Anybody going to ApacheCon Budapest this year? Perhaps we could do a
> little hacking together?
>
> 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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
Antwort: Re: Antwort: Re: Turbine 4.0 M2 Archetype Trunk Release
Posted by Georg Kallidis <gk...@cedis.fu-berlin.de>.
Hi Thomas,
I think it is ok to remove or deprecate TorqueSchedulerService and remove
SQL script generation. If you have a lot of jobs may be it´s useful, but
more appropriate in Fulcrum Quartz or better Fulcrum Security, because of
the dependencies and it´s a kind of security question having scheduled
jobs configuration in a database, isn´t it? ;-).
BTW: In Fulcrum Security the Opensymphony and Turbine Adapters seem to be
deprecated or otherwise removable.
@4.0FinalRelease
I think it would be not a bad idea to set an release date target, e.g. in
December or January for 4.0 final, if it´s only about internal stuff. Then
we could focus, what is really needed, (doing some more cleanup?) ...
@ApacheCon: I should definitely decide it this week (coming to Apache
Core). You could make it? Siegfried as well?
Best regards, Georg
Von: Thomas Vandahl <tv...@apache.org>
An: Turbine Developers List <de...@turbine.apache.org>
Datum: 27.07.2015 19:43
Betreff: Re: Antwort: Re: Turbine 4.0 M2 Archetype Trunk Release
Hi Georg,
On 27.07.15 17:19, Georg Kallidis wrote:
> wow, it seems you updated the scheduler already! Tests are running
> successfully here (Windows, Java 1.7).
Good to know. I guess some docs are still missing.
Do we want to deprecate the TorqueSchedulerService now? If so, I could
remove the whole SQL script generation stuff from the POM and make
Torque an optional dependency. WDYT?
> Do you think Turbine M2 release is ready for take-off (in September or
> earlier)? ;-) We could release the archetype build then soon after this.
Yes, if it's a milestone release. I would like to clean up the module
stuff and RunData/PipelineData mess before going 4.0 final.
> P.S: More upcoming releases are Fulcrum Testcontainer and Yaafi
hopefully.
> Wasn´t a new Fulcrum Script in discussion, of course without backporting
> to Java 8 Nashorn (as far as I know ;-) ..
Anybody going to ApacheCon Budapest this year? Perhaps we could do a
little hacking together?
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: Antwort: Re: Turbine 4.0 M2 Archetype Trunk Release
Posted by Thomas Vandahl <tv...@apache.org>.
Hi Georg,
On 27.07.15 17:19, Georg Kallidis wrote:
> wow, it seems you updated the scheduler already! Tests are running
> successfully here (Windows, Java 1.7).
Good to know. I guess some docs are still missing.
Do we want to deprecate the TorqueSchedulerService now? If so, I could
remove the whole SQL script generation stuff from the POM and make
Torque an optional dependency. WDYT?
> Do you think Turbine M2 release is ready for take-off (in September or
> earlier)? ;-) We could release the archetype build then soon after this.
Yes, if it's a milestone release. I would like to clean up the module
stuff and RunData/PipelineData mess before going 4.0 final.
> P.S: More upcoming releases are Fulcrum Testcontainer and Yaafi hopefully.
> Wasn´t a new Fulcrum Script in discussion, of course without backporting
> to Java 8 Nashorn (as far as I know ;-) ..
Anybody going to ApacheCon Budapest this year? Perhaps we could do a
little hacking together?
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
Antwort: Re: Turbine 4.0 M2 Archetype Trunk Release
Posted by Georg Kallidis <gk...@cedis.fu-berlin.de>.
Hi Thomas,
wow, it seems you updated the scheduler already! Tests are running
successfully here (Windows, Java 1.7).
Do you think Turbine M2 release is ready for take-off (in September or
earlier)? ;-) We could release the archetype build then soon after this.
Best regards, Georg
P.S: More upcoming releases are Fulcrum Testcontainer and Yaafi hopefully.
Wasn´t a new Fulcrum Script in discussion, of course without backporting
to Java 8 Nashorn (as far as I know ;-) ..
Von: Thomas Vandahl <tv...@apache.org>
An: Turbine Developers List <de...@turbine.apache.org>
Datum: 24.07.2015 11:57
Betreff: Re: Turbine 4.0 M2 Archetype Trunk Release
On 22.07.15 09:22, Georg Kallidis wrote:
> Hi,
>
> I have updated the Turbine archetpye trunk (based on Turbine 4 M2),
which
> now fetches the (almost) released Fulcrum security components. I am sure
> the release will be done in the next days ;-) What remains is the
Turbine
> 4 Snapshot itself.
>
> I added before a jetty to quick start. After installing it one could
> immediately see the Turbine app running in the browser, which is by
> default http://localhost:8081/app with mvn jetty:run.
>
> As long as Turbine M2 is not released, the archetype could not, and the
> archetype trunk is only available after checking out and locally
> installing the archetype and retrieving it with mvn archetype:generate
> -DarchetypeCatalog=local.
>
> In my eyes the Turbine 4.0 final release could/should be completed as
soon
> as the Torque 4.1 release is done - or we should better conform and
> release Turbine as 4.1? Should then Turbine 4.0 M2 not get released
soon?
> Having done this would allow to be able again to provide an up-to-date
> archetype = entry point for Turbine 4 M2. The last one based on Turbine
> 4.0 M1 was released in Nov 2012.
I will publish the fulcrum-security artifacts shortly. I'd love to see a
Turbine 4.0 release soon. I would not bet on a Torque 4.1 release in the
near future, so Id rather go with 4.0. This is about the scheduler,
right? I always wanted to replace it with fulcrum-quartz but never got
around to complete it. Any initiative is 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: Turbine 4.0 M2 Archetype Trunk Release
Posted by Thomas Vandahl <tv...@apache.org>.
On 22.07.15 09:22, Georg Kallidis wrote:
> Hi,
>
> I have updated the Turbine archetpye trunk (based on Turbine 4 M2), which
> now fetches the (almost) released Fulcrum security components. I am sure
> the release will be done in the next days ;-) What remains is the Turbine
> 4 Snapshot itself.
>
> I added before a jetty to quick start. After installing it one could
> immediately see the Turbine app running in the browser, which is by
> default http://localhost:8081/app with mvn jetty:run.
>
> As long as Turbine M2 is not released, the archetype could not, and the
> archetype trunk is only available after checking out and locally
> installing the archetype and retrieving it with mvn archetype:generate
> -DarchetypeCatalog=local.
>
> In my eyes the Turbine 4.0 final release could/should be completed as soon
> as the Torque 4.1 release is done - or we should better conform and
> release Turbine as 4.1? Should then Turbine 4.0 M2 not get released soon?
> Having done this would allow to be able again to provide an up-to-date
> archetype = entry point for Turbine 4 M2. The last one based on Turbine
> 4.0 M1 was released in Nov 2012.
I will publish the fulcrum-security artifacts shortly. I'd love to see a
Turbine 4.0 release soon. I would not bet on a Torque 4.1 release in the
near future, so Id rather go with 4.0. This is about the scheduler,
right? I always wanted to replace it with fulcrum-quartz but never got
around to complete it. Any initiative is welcome :-)
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
Turbine 4.0 M2 Archetype Trunk Release
Posted by Georg Kallidis <gk...@cedis.fu-berlin.de>.
Hi,
I have updated the Turbine archetpye trunk (based on Turbine 4 M2), which
now fetches the (almost) released Fulcrum security components. I am sure
the release will be done in the next days ;-) What remains is the Turbine
4 Snapshot itself.
I added before a jetty to quick start. After installing it one could
immediately see the Turbine app running in the browser, which is by
default http://localhost:8081/app with mvn jetty:run.
As long as Turbine M2 is not released, the archetype could not, and the
archetype trunk is only available after checking out and locally
installing the archetype and retrieving it with mvn archetype:generate
-DarchetypeCatalog=local.
In my eyes the Turbine 4.0 final release could/should be completed as soon
as the Torque 4.1 release is done - or we should better conform and
release Turbine as 4.1? Should then Turbine 4.0 M2 not get released soon?
Having done this would allow to be able again to provide an up-to-date
archetype = entry point for Turbine 4 M2. The last one based on Turbine
4.0 M1 was released in Nov 2012.
Any comments?
Best regards, Georg
Turbine 4.0 M2 Archetype (Trunk):
https://svn.apache.org/repos/asf/turbine/maven/archetypes/trunk/turbine-webapp-4.0
.
Von: Thomas Vandahl <tv...@apache.org>
An: Turbine Developers List <de...@turbine.apache.org>,
private@turbine.apache.org
Datum: 20.07.2015 21:40
Betreff: Re: [VOTE] Release fulcrum-security 1.1.0 based on staged
repository
On 19.07.15 21:41, Thomas Vandahl wrote:
> Hi folks,
>
> A release candidate for the Fulcrum Security Components, version 1.1.0
> has been prepared. Please verify this release candidate
> carefully and vote, vote, vote...
>
> Tag:
>
>
https://svn.apache.org/repos/asf/turbine/fulcrum/tags/fulcrum-security-1.1.0
>
> Artifacts:
>
> https://repository.apache.org/content/repositories/orgapacheturbine-1007
Hi folks,
thanks for voting. As this is my first multi-module release, please
check again. Problems are likely, please have a close look.
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
Re: [VOTE] Release fulcrum-security 1.1.0 based on staged repository
Posted by Thomas Vandahl <tv...@apache.org>.
On 19.07.15 21:41, Thomas Vandahl wrote:
> Hi folks,
>
> A release candidate for the Fulcrum Security Components, version 1.1.0
> has been prepared. Please verify this release candidate
> carefully and vote, vote, vote...
>
> Tag:
>
> https://svn.apache.org/repos/asf/turbine/fulcrum/tags/fulcrum-security-1.1.0
>
> Artifacts:
>
> https://repository.apache.org/content/repositories/orgapacheturbine-1007
Hi folks,
thanks for voting. As this is my first multi-module release, please
check again. Problems are likely, please have a close look.
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org