« Return to Thread: FluorineFx v1.0.0.17 SVN
Re: FluorineFx v1.0.0.17 SVN
by Support-179
::
Rate this Message:
Reply (Restricted by the Administrator) | Reply to Author | View in Thread
Hi Chris,
I generally agree with you, let me answer issues related specifically to the
setup: the download section (on both web sites) shows the latest released
installer. Anyone starting with FluorineFx should start with the latest
installer.
The v1.0.0.17 is close to release but without having ready the proper
updated documentation I cannot make a release (hope you understand why).
(Currently in the SVN Rev75 is the latest commit for v1.0.0.16....it is also
labeled as v1.0.0.16)
Thanks,
Zoli
-----Original Message-----
From: fluorine-bounces@...
[mailto:fluorine-bounces@...] On Behalf Of cmatech
Sent: Tuesday, May 05, 2009 5:29 PM
To: Fluorine Mailing List
Subject: Re: [Fluorine] FluorineFx v1.0.0.17 SVN
Zoli,
I think there is a some real confusion on these release cycles.
Example:
1) On the google code site for FluorineFx and there is a downloads tab with
a 1.0.0.15 Setup.exe (which I know you don't want people
using...)
2) On the FluorineFx.com website there is a link to that same download
3) There is no defined release schedule or release target announced.
So users of SVN having a moving target - "do I update and test my codebase
today *or* wait for some unknown changes tomorrow"
4) I have to archive my FluorineFx assemblies (think 1.0.0.16) so I have
something to use in production code - until I have tested and I know that
the 1.0.0.17 code is safe to use for my specific project requirements (For
me personally - it's all RTMP (both client and
server) - and it looks like there are lot of changes).
What I think would help solve this problem would be to use the
*branches* mechanism in SVN - a branch on each release version or at least a
*development* branch and a *release/stable* branch.
This would allow nasty bug fixes to make their way into all branches - but
just development code in the development branch until is officially
"released".
In addition to any binaries (installers/assemblies) in each branch, it would
be nice to have the samples as part of SVN somewhere. As FluorineFx evolves
- so the samples will need to be updated eventually (think config changes).
And it would make them accessible to SVN only developers who do not use the
installers.
Chris
On Tue, May 5, 2009 at 05:24, Support <support@...> wrote:
> Hi Stepan,
>
> I would recommend to go with the SVN version
>
> Zoli
> ________________________________
> From: fluorine-bounces@...
> [mailto:fluorine-bounces@...] On Behalf Of
> Stepan Fryd
> Sent: Saturday, May 02, 2009 12:17 PM
> To: Fluorine Mailing List
> Subject: Re: [Fluorine] FluorineFx v1.0.0.17 SVN
>
> Hi Zolli,
> thank you for message. I am asking because of we are planning to use
> FluorineFX on new project (Windows env.) so I am asking if I can get
> version from SVN or use downloadable version from website (it is
> 1.0.0.15 I guess :|
> )
> Cheers
> Stepan
>
> 2009/5/1 Support <support@...>
>>
>> Hi Stepan,
>>
>> I am not planning to add big changes but keeping it open for bug fixes.
>> (And also working on the new documentation)
>>
>> I know you have been using FluorineFx with mono too but this version
>> was not tested yet with mono.
>>
>> Zoli
>> ________________________________
>> From: fluorine-bounces@...
>> [mailto:fluorine-bounces@...] On Behalf Of
>> Stepan Fryd
>> Sent: Wednesday, April 29, 2009 5:36 PM
>> To: Fluorine Mailing List
>> Subject: Re: [Fluorine] FluorineFx v1.0.0.17 SVN
>>
>> Hi guys,
>> is version 1.0.0.17 stable for production using or is it still under
>> development?
>> Kind regards
>> Stepan
>>
>> 2009/4/20 Support <support@...>
>>>
>>> I've started committing FluorineFx v1.0.0.17 to the SVN
>>>
>>> Here is a short list of changes in this versionÂ
>>> http://www.fluorinefx.com/download/fluorinefx/releasenotes.txt
>>>
>>> There are some breaking changes in the existing API, mainly the
>>> ILoginCommand signature and the Client/Session APIs. For BlazeDS
>>> compatibility there are both IClient and ISession instances created
>>> in the back end (with corresponding IClientListener/ISessionListenerinterfaces).
>>> The previous ISessionListener interface is IClientListener now(!).
>>> Current Client and Session can be accessed through the Fluorine Context.
>>>
>>> Authentication can be also per client or per session (by default is
>>> per
>>> session)
>>>
>>> If you need urgently a fixed version or new features you will have
>>> to use the source code from SVN (binaries are not uploaded yet). I
>>> still have to check some reported problems and finish the new
>>> documentation, only after that a new installer will be provided.
>>>
>>> Zoli
>>>
>>> _______________________________________________
>>> fluorine mailing list
>>> fluorine@...
>>>
>>> http://fluorine.thesilentgroup.com/mailman/listinfo/fluorine_fluorin
>>> e.thesilentgroup.com
>>>
>>
>>
>> _______________________________________________
>> fluorine mailing list
>> fluorine@...
>>
>> http://fluorine.thesilentgroup.com/mailman/listinfo/fluorine_fluorine
>> .thesilentgroup.com
>>
>
>
> _______________________________________________
> fluorine mailing list
> fluorine@...
> http://fluorine.thesilentgroup.com/mailman/listinfo/fluorine_fluorine.
> thesilentgroup.com
>
>
_______________________________________________
fluorine mailing list
fluorine@...
http://fluorine.thesilentgroup.com/mailman/listinfo/fluorine_fluorine.thesil
entgroup.com
_______________________________________________
fluorine mailing list
fluorine@...
http://fluorine.thesilentgroup.com/mailman/listinfo/fluorine_fluorine.thesilentgroup.com
I generally agree with you, let me answer issues related specifically to the
setup: the download section (on both web sites) shows the latest released
installer. Anyone starting with FluorineFx should start with the latest
installer.
The v1.0.0.17 is close to release but without having ready the proper
updated documentation I cannot make a release (hope you understand why).
(Currently in the SVN Rev75 is the latest commit for v1.0.0.16....it is also
labeled as v1.0.0.16)
Thanks,
Zoli
-----Original Message-----
From: fluorine-bounces@...
[mailto:fluorine-bounces@...] On Behalf Of cmatech
Sent: Tuesday, May 05, 2009 5:29 PM
To: Fluorine Mailing List
Subject: Re: [Fluorine] FluorineFx v1.0.0.17 SVN
Zoli,
I think there is a some real confusion on these release cycles.
Example:
1) On the google code site for FluorineFx and there is a downloads tab with
a 1.0.0.15 Setup.exe (which I know you don't want people
using...)
2) On the FluorineFx.com website there is a link to that same download
3) There is no defined release schedule or release target announced.
So users of SVN having a moving target - "do I update and test my codebase
today *or* wait for some unknown changes tomorrow"
4) I have to archive my FluorineFx assemblies (think 1.0.0.16) so I have
something to use in production code - until I have tested and I know that
the 1.0.0.17 code is safe to use for my specific project requirements (For
me personally - it's all RTMP (both client and
server) - and it looks like there are lot of changes).
What I think would help solve this problem would be to use the
*branches* mechanism in SVN - a branch on each release version or at least a
*development* branch and a *release/stable* branch.
This would allow nasty bug fixes to make their way into all branches - but
just development code in the development branch until is officially
"released".
In addition to any binaries (installers/assemblies) in each branch, it would
be nice to have the samples as part of SVN somewhere. As FluorineFx evolves
- so the samples will need to be updated eventually (think config changes).
And it would make them accessible to SVN only developers who do not use the
installers.
Chris
On Tue, May 5, 2009 at 05:24, Support <support@...> wrote:
> Hi Stepan,
>
> I would recommend to go with the SVN version
>
> Zoli
> ________________________________
> From: fluorine-bounces@...
> [mailto:fluorine-bounces@...] On Behalf Of
> Stepan Fryd
> Sent: Saturday, May 02, 2009 12:17 PM
> To: Fluorine Mailing List
> Subject: Re: [Fluorine] FluorineFx v1.0.0.17 SVN
>
> Hi Zolli,
> thank you for message. I am asking because of we are planning to use
> FluorineFX on new project (Windows env.) so I am asking if I can get
> version from SVN or use downloadable version from website (it is
> 1.0.0.15 I guess :|
> )
> Cheers
> Stepan
>
> 2009/5/1 Support <support@...>
>>
>> Hi Stepan,
>>
>> I am not planning to add big changes but keeping it open for bug fixes.
>> (And also working on the new documentation)
>>
>> I know you have been using FluorineFx with mono too but this version
>> was not tested yet with mono.
>>
>> Zoli
>> ________________________________
>> From: fluorine-bounces@...
>> [mailto:fluorine-bounces@...] On Behalf Of
>> Stepan Fryd
>> Sent: Wednesday, April 29, 2009 5:36 PM
>> To: Fluorine Mailing List
>> Subject: Re: [Fluorine] FluorineFx v1.0.0.17 SVN
>>
>> Hi guys,
>> is version 1.0.0.17 stable for production using or is it still under
>> development?
>> Kind regards
>> Stepan
>>
>> 2009/4/20 Support <support@...>
>>>
>>> I've started committing FluorineFx v1.0.0.17 to the SVN
>>>
>>> Here is a short list of changes in this versionÂ
>>> http://www.fluorinefx.com/download/fluorinefx/releasenotes.txt
>>>
>>> There are some breaking changes in the existing API, mainly the
>>> ILoginCommand signature and the Client/Session APIs. For BlazeDS
>>> compatibility there are both IClient and ISession instances created
>>> in the back end (with corresponding IClientListener/ISessionListener
>>> The previous ISessionListener interface is IClientListener now(!).
>>> Current Client and Session can be accessed through the Fluorine Context.
>>>
>>> Authentication can be also per client or per session (by default is
>>> per
>>> session)
>>>
>>> If you need urgently a fixed version or new features you will have
>>> to use the source code from SVN (binaries are not uploaded yet). I
>>> still have to check some reported problems and finish the new
>>> documentation, only after that a new installer will be provided.
>>>
>>> Zoli
>>>
>>> _______________________________________________
>>> fluorine mailing list
>>> fluorine@...
>>>
>>> http://fluorine.thesilentgroup.com/mailman/listinfo/fluorine_fluorin
>>> e.thesilentgroup.com
>>>
>>
>>
>> _______________________________________________
>> fluorine mailing list
>> fluorine@...
>>
>> http://fluorine.thesilentgroup.com/mailman/listinfo/fluorine_fluorine
>> .thesilentgroup.com
>>
>
>
> _______________________________________________
> fluorine mailing list
> fluorine@...
> http://fluorine.thesilentgroup.com/mailman/listinfo/fluorine_fluorine.
> thesilentgroup.com
>
>
_______________________________________________
fluorine mailing list
fluorine@...
http://fluorine.thesilentgroup.com/mailman/listinfo/fluorine_fluorine.thesil
entgroup.com
_______________________________________________
fluorine mailing list
fluorine@...
http://fluorine.thesilentgroup.com/mailman/listinfo/fluorine_fluorine.thesilentgroup.com
« Return to Thread: FluorineFx v1.0.0.17 SVN
| Free embeddable forum powered by Nabble | Forum Help |
