issue-#112 revisited

Post Reply
User avatar
Josef Templ
Posts: 2047
Joined: Tue Sep 17, 2013 6:50 am

issue-#112 revisited

Post by Josef Templ »

I have increased the changelist limit from 100 to 200 issues.
This is important because issue-#121 is really above 100.
For the changes in the build script and SriptChanges.odc see the diffs at
http://redmine.blackboxframework.org/pr ... 87783e090e.

By limiting the issues to 200 (using two files instead of one) it was possible to keep the complexity reasonably small. An arbitrary upper bound would be more complicated.

- Josef
User avatar
Josef Templ
Posts: 2047
Joined: Tue Sep 17, 2013 6:50 am

Re: issue-#112 revisited

Post by Josef Templ »

let us proceed with the voting on this.
It is about increasing the number of change list entries from 100 to 200.
This change is already activated as part of the build engine on our Edis host
but it is not yet merged to master.

We should also proceed with the voting on #122 (Conerter.next)
and then we should proceed with the step from rc1 to final.

- Josef
User avatar
Robert
Posts: 1024
Joined: Sat Sep 28, 2013 11:04 am
Location: Edinburgh, Scotland

Re: issue-#112 revisited

Post by Robert »

Josef Templ wrote:... proceed with the step from rc1 to final.
It sounds good to read this - well done all.

Is final the best name - what about stable?
User avatar
Josef Templ
Posts: 2047
Joined: Tue Sep 17, 2013 6:50 am

Re: issue-#112 revisited

Post by Josef Templ »

With final I mean to remove the phase part (a1, b1, rc1, etc.) in the naming of the resulting files
(zip, exe, build log, change log).

FYI: This results from updating the content of the file appbuild/AppVersion.txt from '1.7-rc1' to '1.7'.
The build output will then be put into the directory named 'stable' by the build engine, hopefully.
We have not done extensive tests with building a final release because there was none until now.
Since there are only minor modifications between building an unstable and a stable version, I
don't expect any major problems.

We will also put a tag into the github repository after we reached the final stage.

- Josef
Post Reply