Yes exactly @Nitish, I want their corporate decisions to be open-sourced
as well! ;-]
@AW, I can understand the rationale - given your workflow - for thinking
production releases as rather redundant.
I think my feedback on the subject has focused more on the marketing
side of things: That it's good for the overall enthusiasm of the
community to "draw that line" once in a while and update the site to
show some evolution - regardless of the literal state of the code itself.
That, OR to update the site - to actually say what you said below - and
remove the whole "this version is production, this version is not"
jargon & links.
Sorry to elbow my way into your boardroom, and thanks for all you guys
do. Now close discussion and call for a vote. I move to adjourn...
AH
On 4/14/2014 6:52 AM, Alan Williamson wrote:
nothing too sinister.
with our project, we rarely release stuff to the nightly build that
isn't production ready. We do testing internally before we get to
that stage, so by the time it is released to the community its ready
to go.
So really a release is merely drawing a line in the sand and giving it
a name. the code is the precise same as the nightly build.
On 11/04/2014 15:57, Alan Holden wrote:
If possible, can you share the arguments on each side of your debate?
Perhaps bringing them out into the light will help you move one way
or the other.
Al
On 4/8/2014 3:42 AM, Alan Williamson wrote:
we're still debating whether or not we have a formal releases.
--
--
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.
