Circuits 1.6 vs development branch

[Kyle Jordan]

Hi,

  We are looking at Circuits as a solution for our event driven framework.  Our application is on an embedded device and we really like some of the features Circuits offers in a lightweight package.  Since this is an embedded application, stability is a major requirement for us.  I saw a post in the mailing list asking about using Circuits 1.6 or the development branch, and the development branch was suggested.  I typically prefer to use the stable releases instead of a development branch, but in this case is there an advantage to using the development branch in terms of stability?  Was that suggestion due to new features of the development branch?

Thanks,

Kyle Jordan
Senior Software Engineer

L.B. Foster Company - Salient Systems
4393-K Tuller Rd
Dublin, OH  43017-5008
phone: (614) 792-5800  EX 4637
fax: (614) 792-5888
email: kjo...@salientsystems.com

website:  www.lbfoster.com
NASDAQ Ticker Symbol: FSTR

[James Mills]

Hi Kyle,

Thanks for your interest in circuits!

Whilst the development branch is actively in "development"

it does contains new features (some of which you may find useful)

as well as lots of bug fixes and cleanups.

We are in fact readying the circuits-dev branch for release soon

with the upcoming circuits-1.7. As such I would recommend you

use the development branch at this time as we're so near to

release anyway (There are some backwards incompatible changes

from 1.6 -> 1.7).

Rest assured however, we do test-driven development with

circuits and circuits has over 200+ unit tests testing over 80%

of the code base. (We'd like that to be 100% but we'll get there!)

FYI, others have also used circuits for embedded devices

in other projects.

Good luck! Questions, feedback welcome!

We're also on IRC (Freenode) if you need more real-time support.

cheers

James

James Mills / prologic

Developer | circuits, sahriswiki
E: prol...@shortcircuit.net.au

S: therealprologic

W: softcircuit.com.au

--
You received this message because you are subscribed to the Google Groups "circuits" group.
To post to this group, send email to circuit...@googlegroups.com.
To unsubscribe from this group, send email to circuits-user...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/circuits-users?hl=en.

[Kyle Jordan]

James,
   Thanks for the reply.  How close are you to releasing circuits 1.7?  We are looking to release our product on July 1 and we would prefer to have the released circuits 1.7 at that time.

Thanks,

Kyle Jordan
Senior Software Engineer

L.B. Foster Company - Salient Systems
4393-K Tuller Rd
Dublin, OH  43017-5008
phone: (614) 792-5800  EX 4637
fax: (614) 792-5888
email: kjo...@salientsystems.com

website:  www.lbfoster.com
NASDAQ Ticker Symbol: FSTR

[James Mills]

It was planned for this weekend.

We'll see how we go.

But it'll be well before July.

cheers

James

James Mills / prologic

Developer | circuits, sahriswiki
E: prol...@shortcircuit.net.au

S: therealprologic

W: softcircuit.com.au

[Alessio Deiana]

As far as I know we wanted to be update the documentation before releasing the new version, the code itself behing ready.

On Tuesday, July 17, 2012 9:42:41 PM UTC+2, aspidites wrote:

July is half-way over and there has yet to be a release. :-( Is there a list of tasks that need to be completed before a release is possible? I'm mostly interested in the supposed changes in channels and the accompanying documentation (or is the 1.6 documentation representative of how channels operate in the current dev branch?

[aspidites]

Ah. Wish I had a better understanding of the internals. I'd offer to help. Maybe once API doc is updated I can see about writing a tutorial or something? (or updating the current one)