John .. thank you.
The key with any software is testing. We are not checking code into
the nightly build without doing our extensive testing first.
But you ALWAYS have to do your own testing, whether it is the nightly
release, or a stable build before you go to production with your code.
If you are looking to just blindly drop in a new release (nightly or
otherwise) then you are on a hiding to nothing.
So the 'stable release' from time-2-time serves no real purpose in our
world, since there isn't a huge architectural change under the
covers. If we decide to do something big and rewrite a major
component, then yes, we would branch that in GitHub and continue with that.
To be frank, calling it 'nightly builds' is a bit of a misleading term
.. it is more building against the latest code. We are not checking
into GitHub until we are completely satisfied that everything is perfect
as best as we can tell. The good news with GitHub is that it makes
REAL easy to pull a previous version of the software. We're using the
services of GitHub as a release management system.
So let us stop calling it the nightly-build and simply say the latest build.
But irrespective of what code you update from, you always should do your
own testing and be satisfied with the code. Anyone will tell you that
even the big groups have problems, we've had many a time where we had to
roll back to a previous MySQL, Mongo, etc because their stable release
had a problem.
Hope this helps
On 21-Apr-16 09:29, John Moss wrote:
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?
--
--
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.
