Hi Alan, You say "NO" but the rest of your reply says "YES." I'm sorry, but that's the way I read it.
We have a problem with the "Nightly Build" process: there have been a number of times when I have seen people say something is broken in the nightly build, and I can disregard it because I don't use the nightly build. I can't afford to have something break in our system because we loaded something from a nightly build. For this reason I believe it is prudent to have a "stable release" from time to time. I will only run software on a production server if it comes from a stable release which has been around and tested for a while, and I am relatively certain that it is not going to fail us. I know this is not a democracy but that's my 2 cents. Our company runs on OpenBD--we have written lots of code that we know works in that environment. Is there something I could do to help? On Monday, April 18, 2016 at 9:48:51 AM UTC-6, Alan Williamson wrote: > > Charles thank you for your email. > > The question is OpenBD dead? NO. > > There has been no stable release for a number of years, and there won't > be another one. I stated in an email many years ago that we wouldn't > be releasing any more official releases, but instead instructed people > to use the "nightly" release. The code base is that stable and mature, > we are not making any huge changes to it. > > In short ... it just works. aw2.0 is still using OpenBD actively in > their projects as are many thousands of others. We are make small > changes/fixes as and when they are reported. But the reality is that > show-stopping bugs are rare and far between these days. > > But with the advent of richer/fatter clients .. the role of the server > side is diminishing. That is a sad fact, but the reality of web > development today. > > So do we want to evolve and add new features to OpenBD? Well to be > frank yes, but no at the same time. We don't want to waste time > building new features only for the web development world to move forward > and make that irrelevant (CFWINDOW/CFFORM anyone?!?!?). > > To add to Marcus's point ... the project is hosted in GitHub. That > means it is available to ANYONE to pick up and add new features. We are > more than happy to review and accept submissions to the core branch. > There is ZERO barrier to contribution. > > At the end of the day, every user of OpenBD (or any software) has to > decide if it is for them or not. Where is your web development going? > Where are you innovating? What type of apps are you being asked to > write now compared to what you were doing maybe 5-10 years ago? These > are all questions you need to be asking on a weekly basis to make sure > you are keeping relevant and servicing your clients to the best. > > Hope that helps. > > On 17-Apr-16 12:42, Skellington wrote: > > Hello, > > I'm really curious about this. Is OpenBD dead, or will the product > > grow and evolve? There has not been a stable release in a couple of > > years. The release notes used to be updated with dates and no longer > > do. I'm really on the fence here and in no way am I knocking the > > OpenBD product. I've been using it since it was released and it's > > worked really well for me. My real growing concern is if it's not > > being developed and it's kinda being sun setted should I be looking at > > migrating to something like Lucee? > > -- -- online documentation: http://openbd.org/manual/ http://groups.google.com/group/openbd?hl=en --- You received this message because you are subscribed to the Google Groups "Open BlueDragon" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
