Fiware Cepheus home page says that its branch is archived and 'read only' now.
https://github.com/Orange-OpenSource/fiware-cepheus
So does it mean:
1. There would be no future support and development in this community?
2. As alternative we should use 'Perseo' as its similar in functionality
https://perseo.readthedocs.io/en/latest/
In general, archiving a GitHub project means that "the project is no longer actively maintained.https://help.github.com/en/articles/about-archiving-repositories
The Fiware Cepheus page also states that "no new features will be added, nor issues fixed by the original team." So this means option 1 is the answer to your question.
There exists 21 forks of this project, so perhaps the community is moving over to one of those?
I am not familiar with 'Perseo', so I cannot tell you if option 2 is a good solution or not.
Yes, further information can be found in the FIWARE 7.4 Release Note
As announced at the Porto Global Summit 2018, five generic enablers
were placed under analysis and have subsequently been removed:
Proton, 3D-UI, FiVES, Cepheus, Aeron IoT Broker
Perseo is the now the
preferred generic enabler for complex event processing, replacing
Proton and Cepheus. 3D-UI. FiVES and Aeron are no longer seen to be a
good fit with the FIWARE project.
If you want to use Complex Event Processing you are left with two choices:
Convert your project to use Perseo and continue to enjoy community support and development.
Continue to use an archived CEP processor, fork it and make further bug fixes on your own.
Related
I'm interested in using Rubberduck primarily for it's Github source control feature. However, from looking at the Github site for the project I can see that in the most recent versions that feature is not so stable. My question is, what version should I use? For now all I really care about is to have the most stable source control feature. Should I go back as far as v1.4.3? Or is there another 2.X version that was more stable before things recently got worse?
EDIT: As per Vogel's comment
This answer is outdate since a few months: Source control has been
removed completely in the PR #3782 on Feb 26 2018
Even so...
I'd definitely recommend trying out Rubberduck; the unit testing, code inspection and other features are awesome... also the guys involved are generous with sharing their time and knowledge - but IMHO would shy away from using an old version to gain access to the Git features (it has been disabled for a reason).
You can enable it as an 'Experimental Feature' under the menu system > Rubberduck > Settings > General Settings (scroll down)
If you really need something ASAP perhaps look at VBAdiff (http://vbadiff.com/) or this project https://github.com/spences10/VBA-IDE-Code-Export
The bulk of the efforts of the past couple of months went to perfecting the parser and resolver, which impacts overall performance and all inspections and refactoring features; eliminating inspection false positives and making sure no quickfix or refactoring wrecked our users' code has been the top priority, leaving the borked source control panel under-loved - so much that we recently outright disabled it by default, until we git it under control.
Teams mean to grow, and a new contributor joined the project and started working on the source control panel issues.
A pull request was merged recently,
and since every merged PR gets a prerelease CI build published, v2.1.0.2257 is now available for download.
This fixes an IoC registration bug involving an abstract factory interface that the SC panel uses, and it just so happens to apparently fix the exceptions with GitHub authentication, so pushing should now work fine.
More fixes on the way, v2.1 "green release" will likely have a pretty much stable source control feature =)
Is is possible to do force directed edge bundling in gephi? I see a GSOC project completed in 2013 but I want to know if it is packaged with the standard release now. If yes, how to use it?
Thanks a lot for the help
It's possible in a demo build only. The project you refer to has been integrated into this demo build (a little over a year old, though). According to the developers, other things have to be addressed first before this makes it into the regular build. There is no estimated ship date.
I am looking for documentation for Ace to do "Floating UI" , i want to to like facebook "Chat Heads". So far there is no documentation only mentioning coming soon , which means avaliable but undocumented right?. Is it already available in github latest master?
They decided to close the support for this project:
As of December 2016, this project is no longer maintained by Microsoft. We built ACE to provide developers with an “escape hatch” to access native code from within JavaScript. After nearly a year in production, we learned that most developers are satisfied with the access granted by Cordova’s Plugin Model. Thus, we’ve discontinued active development. We appreciate your interest in the project and hope you found it exemplary of Microsoft’s commitment to experimentation and open source software. if you're interested in continuing this project, please feel free to fork it. As of December 2016, we will no longer monitor or respond to open issues. You can keep up with other projects from Microsoft’s Cordova team by visiting http://taco.visualstudio.com. Thanks for your support!
I was also looking some plugin to implement "chat heads" in Cordova, without any luck :(
I have installed the Zeos 7 Beta on my own machine but it fails on my client's laptop. We're both running Delphi xe2, his is Entreprise, mine is Pro. His machine is running 64-bit windows 7, mine is running Window 7 32-bit.
When I do Compile all on ZeosDbo or ProjectGoup16 it seems to get through ZCore.dpk but then shows 2 fatal errors:
ZCore.dpk(1) E2225 Never-build package 'ZCore' must be recompiled
ZParseSQL.dpk(33) E2202 Required package 'ZCore' not found
This is production code we are working on, so I hope we can find a solution and get back to working on this
Zeos forum thread: http://zeos.firmos.at/viewtopic.php?t=3633
That is one error, the 1st one. The second is merely post-effect.
Perhaps you can do better than downloading beta ZIPs: until they have mature release you just can download each day "nightly" changes by version-control tools, like Git or SVN or whatever Zeos team is using.
Such errors are usually quickly fixed (they are simple) but long released(they are so moot that no one would bother making release for them).
Just open http://zeos.firmos.at/portal.php and read where to get most instant updates and how to report problems.
Actually - there it is, http://svn.code.sf.net/p/zeoslib/code-0/trunk/
Install TortoiseSVN and be on the edge until 7.0.1 or 7.0.2 final release
The page also says: Please report bugs for this version to our brand new bugtracker on sourceforge https://sourceforge.net/p/zeoslib/tickets/
Please do. Open Source is about participating. At least participate by registering bugs.
About the essence of problem read official documentation and "See Also" section.
Someone should decide about package binary update strategy. And the decision should be kept for all packages (okay, you can mix it in some conditions, but that is not to be suggested). So basically you have three choices:
Make your own decision and put all Zeos packages into the strategy of your choice. That puts the responsibility upon yourself to maintain this fork for a while until you come back to vanilla ZeosDB.
Report the bug to ZeosDB team and ask their suggestion, then change those settings for all the packages as suggested by them.
Report the bug to ZeosDB team and wait until they'd fix it in their SVN and then do SVN Update.
Personally i'd go with 1 option, but i am ready to be FLOSS libraries co-developer.
Option 3 would be the most slow yet the most easy for you.
Option 2... well... i can not see why you should choose that, except for trying to avoid version controls at any cost, which is bad idea per se.
I also suggest you to read http://www.catb.org/esr/faqs/smart-questions.html
That would help you effectively communicate at ZeosDB forums - and you'd have to if you want to be "on the edge" (and if you do not - then wait for public release like 7.0.2).
The accepted answer to this question suggests using an SVN revision number as part of the version number when building a release. I want to do something similar using Team Coherence, which doesn't do revision numbers quite the same way.
For Delphi 2009 how can I set up a build script so that every release automatically includes a number or tag linking it to a specific Team Coherence check-in or version label? Just a way to access the current version label would be great, though a solution that automatically updates it would be even better.
I don't know how to do this (though I'm interested in the answer, I use TC myself) - but have you emailed Ewan at QSC about it? On the few occasions I've needed some help doing something like this he's replied very quickly and if he doesn't know how to do it, well quite honestly you probably can't - he's the TC developer! :-)
support#teamcoherence.com
QSC web site