BlackBox Framework Center

DGDanforth wrote:Does anyone have a tool (utility) that can recompile all modules?

see http://www.zinnamturm.eu/downloadsAC.htm#Bbt
und run (!)"BbtCompLists.BuildFullCompileList"

You may compare the Center Edition Beta 513 with the CPC Edition 1604 (16 = year 2016 and 04 = April).

- Helmut

There are some procedural issues with going to beta.

For going to beta we need to update AppVersion.txt.
This is a merge to master in the repository.
Such a merge to master needs a vote.
Such a vote makes it clear that the center members agree to switching to beta.

It is not up to the chairman or anybody else to decide
to make this step. So in the future please stick to the rules.

- Josef

DGDanforth wrote:By the way,
Does anyone have a tool (utility) that can recompile all modules?
Required:
(1) Enter (or browse to) top level directory and hit Compile
(2) have that tool search all sub "Mod" directories
(3) Open all .odc in Mod aan obtain IMPORT list
(4) Sort all those imports into compilation order
(5) Compile as much as possible but don't halt on a failure but rather put the file name into a failure list (document)
(6) Continue until done.

-Doug

Yes.
I am in S Spain on a motor cycling trip at the moment so can't publish it for a couple of weeks anyway.
I

Ivan Denisov wrote:This is first beta version:
http://blackboxframework.org/unstable/m ... b1.513.zip
http://blackboxframework.org/unstable/m ... -setup.exe

Should we reset the build number?

Very pleasant news!

Josef Templ wrote:There are some procedural issues with going to beta.

For going to beta we need to update AppVersion.txt.
This is a merge to master in the repository.
Such a merge to master needs a vote.
Such a vote makes it clear that the center members agree to switching to beta.

It is not up to the chairman or anybody else to decide
to make this step. So in the future please stick to the rules.

I should agree with you, that this step could be voted. However, really it is de facto beta without any announced or pending features. So changing of this file is just a technical marking-out work done by me as a technician. As a chairman whom aim is to release BlackBox until July I am appealing to keep "feature freeze" condition about 1.7 version. All further discussions of features should be referenced to 1.8 version if we want to release any product this summer.

Josef, what do you think about build number?

DGDanforth wrote:Does anyone have a tool (utility) that can recompile all modules?

ypkDevTool allows to compile several subsystems at one time automatically resolving the import list dependencies.

Compilation list and example you will find in: DevTool-Quick-Start.odc

Ivan Denisov wrote: I should agree with you, that this step could be voted. However, really it is de facto beta without any announced or pending features. So changing of this file is just a technical markdown work done by me as a technician. As a chairman whom aim is to release BlackBox until July I am appealing to keep "feature freeze" condition about 1.7 version. All further discussions of features should be referenced to 1.8 version if we want to release any product this summer.

Josef, what do you think about build number?

The build number must not be changed in any way.
It simply counts up. No special rule or exception required.
Resetting the build number would result in ambiguities, obviously!

IMHO, everything continues as it was. We use issues for discussing/resolving
upcoming problems no matter if we are in alpha or beta phase.
We use a Refs. #XXX. for EVERY commit.
Most issues will already exist in redmine, e.g #49.
We should not introduce new numbers for revisiting existing issues.

Any new feature proposals should be postponed for now in order to focus on
finishing the release.

- Josef

Let's accumulate our experiences about migration here:
http://wiki.blackboxframework.org/index ... uilder_1.7

Can someone, please, check my language here and fix? Are there something to add?

Zinn wrote:

DGDanforth wrote:Does anyone have a tool (utility) that can recompile all modules?

see http://www.zinnamturm.eu/downloadsAC.htm#Bbt
und run (!)"BbtCompLists.BuildFullCompileList"

You may compare the Center Edition Beta 513 with the CPC Edition 1604 (16 = year 2016 and 04 = April).

- Helmut

Helmut,
Thanks. Nice but not sufficient. The compilation process stops when a compile does not succeed.
That is not acceptable when one has 1,800+ files to compile with 400+ that are out of date.
One needs to simply flag the bad files and continue compilation.
-Doug