Re: Antwort: Re: [DISCUSS] Fulcrum Intake Release before Turbine 4.0.1?

2018-02-05 Thread Jeffery Painter

Hi guys,

If Thomas is happy with the last patch I submitted for Intake, I don't 
have anything more to contribute at the moment to stop us from doing 
some point releases. I am running with all the SNAPSHOTs for my users 
the past week or so and no complaints so far :-) The parallel deployment 
option is again working for me, so I am happy.


I know that the Turbine quarterly report is due soon (2 days?). Let me 
know if there is anything else I can do to help.


--
Jeff


On 02/05/2018 02:24 AM, Georg Kallidis wrote:

Hi Thomas,


I think that an Intake release makes every sense.
As Intake is usually my playground, I'll do the release.

Thanks for taking this over!


I have some adjustments sitting here regarding Velocity 2.0. These are
not yet committed as Velocity 2 needs at least Java 1.7. If you think
that updating the Java requirements in a bugfix release is a good idea
(which I don't), I'm ready to commit the changes.

That´s another reason, why I want to release the bugfix release (4.0.1)
soon.
Java version should not be changed, until this is done - but not very much
longer.
Your announcements are very welcome, of course!

Best regards, Georg



Von:Thomas Vandahl 
An: Turbine Developers List 
Datum:  04.02.2018 12:43
Betreff:Re: [DISCUSS] Fulcrum Intake Release before Turbine 4.0.1?



On 02.02.18 10:06, Georg Kallidis wrote:

Fulcrum Security is just released, but not yet Intake. Intake would be
just a bugfix release - or not? Then who may trigger the voting process?
Jeff?

I think that an Intake release makes every sense.
As Intake is usually my playground, I'll do the release.


We may update the trunk to Java 8 (and update minor/major version number

-

we may also create a branch for 4.0.x).

I have some adjustments sitting here regarding Velocity 2.0. These are
not yet committed as Velocity 2 needs at least Java 1.7. If you think
that updating the Java requirements in a bugfix release is a good idea
(which I don't), I'm ready to commit the changes.

Bye, Thomas.


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





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



Antwort: Re: [DISCUSS] Fulcrum Intake Release before Turbine 4.0.1?

2018-02-04 Thread Georg Kallidis
Hi Thomas,

> I think that an Intake release makes every sense.
> As Intake is usually my playground, I'll do the release.

Thanks for taking this over!

> I have some adjustments sitting here regarding Velocity 2.0. These are
> not yet committed as Velocity 2 needs at least Java 1.7. If you think
> that updating the Java requirements in a bugfix release is a good idea
> (which I don't), I'm ready to commit the changes.

That´s another reason, why I want to release the bugfix release (4.0.1) 
soon. 
Java version should not be changed, until this is done - but not very much 
longer.
Your announcements are very welcome, of course!

Best regards, Georg



Von:Thomas Vandahl 
An: Turbine Developers List 
Datum:  04.02.2018 12:43
Betreff:Re: [DISCUSS] Fulcrum Intake Release before Turbine 4.0.1?



On 02.02.18 10:06, Georg Kallidis wrote:
> Fulcrum Security is just released, but not yet Intake. Intake would be 
> just a bugfix release - or not? Then who may trigger the voting process? 

> Jeff?

I think that an Intake release makes every sense.
As Intake is usually my playground, I'll do the release.

> We may update the trunk to Java 8 (and update minor/major version number 
- 
> we may also create a branch for 4.0.x). 

I have some adjustments sitting here regarding Velocity 2.0. These are
not yet committed as Velocity 2 needs at least Java 1.7. If you think
that updating the Java requirements in a bugfix release is a good idea
(which I don't), I'm ready to commit the changes.

Bye, Thomas.


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




smime.p7s
Description: S/MIME Cryptographic Signature