The OpenBD administrator (the CFAdmin-like app that edits the xml
file(s) for us) was a collective labor of love - headed up by Matt
Woodward as I recall...
I'll bet it wouldn't be that hard for some of us to write some CF
scripts to add to that admin directory, which could (download and)
expand a stable release file, then put all the eggs in the proper
baskets automatically for us. It's what we know: CFML to update the
CFML engine...
Al
On 3/11/2014 2:27 PM, Dante wrote:
Yes, I know that...
But sometimes changes things on the "webresources"
folder... for instance.
I just think that it will be easyer if this kind of
upgrades could be done more automatically...
BTW, this is not a big problem....
Dante
On Tuesday, March 11, 2014 5:09:32 PM UTC-3, MiniFireDragon
wrote:
Once you get passed a certain release (I think it was
just before 3.0) all I have to do is copy the lib
folder. Never had a problem.
On 3/11/2014 3:17 PM, Dante wrote:
Hello
In my experiencie, is something hard to upgrade the
OpenBD version.
I usually have to back up all the website, and
copy side by side the WEB-INF/bluedragon folder,
taking care to not overwrite the bluedragon.xml
file, Copying also the /lib/ folder (restoring some
jars that I use), etc etc.
If the OpenBD upgrade process were more easy, I
will be upgrading often :)
But the most interesting thing for me is to see
some kind of periodically update from the developer
sites. It can be some tweets, blog, or something
similar. Because the feeling of being "alone" is
frustrating sometimes.
Dante
PS: And,yes, sorry for my poor english.
On Tuesday, March 11, 2014 2:16:43 PM UTC-3, Alan
Williamson wrote:
That is
probably not a bad idea ... there is a lot of
commits still going on ...
On 11/03/2014 12:26, Jason King wrote:
I agree with AH.
Perhaps there should be a rule of thumb that
every 3 months, the latest nightly build is
bundled up and presented as the YY.X version
(year, release). Maybe like 14.1, 14.2.
I don't know. But I think there's too much
going on behind the scenes without any
public updates. The waters appear quieter
than they really are. The project needs some
splash!
On Tue, Mar 11,
2014 at 11:19 AM, Alan Holden <[email protected]>
wrote:
Alan's post that Andy references - was
in response to something I wrote (I'm
a different, less-skilled Alan, which
can be confusing at times).
While I applaud the team's commitment
to OpenBD, and the frequent nightly
builds, I still wish that AW would
bundle up and make a "real release"
perhaps once a year or so. It would
freshen the site for the masses - even
if the application of a pretty version
number was more academic.
Al
--
--
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.
--
--
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 openbd+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
--
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.
--
--
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.
|