Page 2 of 3

Re: #1 DevCPT bug

Posted: Sun Aug 10, 2014 4:21 am
by ReneK
I agree and will start the voting as soon as I'm on my pc (monday).

Re: #1 DevCPT bug

Posted: Sun Sep 07, 2014 11:56 am
by Ivan Denisov
ReneK wrote:I agree and will start the voting as soon as I'm on my pc (monday).
Doug, I think that the time comes for you to make this poll.

Re: #1 DevCPT bug

Posted: Sun Sep 07, 2014 6:07 pm
by DGDanforth
Does anyone object to this issue being being put to a vote?

Re: #1 DevCPT bug

Posted: Sun Sep 07, 2014 6:12 pm
by ReneK
I think we had a rule that if three members want a vote, the vote should be started.

Re: #1 DevCPT bug

Posted: Wed Sep 17, 2014 12:20 pm
by Ivan Denisov
Congratulations! Both votes (1, 2) are finished according to the "Short Circuit" rule. We can merge the first bug fix in Center version.
Josef, can you do this?

Re: #1 DevCPT bug

Posted: Wed Sep 17, 2014 5:14 pm
by DGDanforth
Ivan Denisov wrote:Congratulations! Both votes (1, 2) are finished according to the "Short Circuit" rule. We can merge the first bug fix in Center version.
Josef, can you do this?
I have locked both polls.
Good going guys!

Re: #1 DevCPT bug

Posted: Wed Sep 17, 2014 8:17 pm
by Josef Templ
I have merged issue-#13 into master.

Folks, this is a historic moment.
We have agreed on the first bug fix that will go into the next release.
The bug fix has been merged into master and the build engine has
built a new unstable release.
"A small step for a build engine but a giant leap for BlackBox." ;-)

The build engine has created the new release available under
http://blackboxframework.org/unstable/m ... a1.006.zip.

Why did the build engine create a new release?
Because there was a commit to one of the branches, it was master in this example.
Merging a pull request in Git is also a commit, i.e. a new revision is created.

Why did the build engine output the new release in folder .../unstable/master?
Because it is not a final release as indicated by the current value of the file
appbuild/AppVersion.txt. This is set to '1.7-a1', which means alpha 1, or in other
words: the first round of working on the 1.7 alpha release. An alpha release means
that it is not feature complete, it is been actively worked on, it is primarily intended for
internal (Center) testing.
The build engine put the output into sub-folder master because this is the
name of the branch the commit happened in.

What is 006?
This is the build number, which is a global number incremented per build.
This number guarantees that the output of the build engine always uses a unique file name.

More details of the build engine and the development process can be found in our Wiki.

Last but not least I would like to emphasize that this bug fix was a nice example for synergy
that can happen in a community. The original bug fix was already quite clean
but has been improved by Chris in a remarkable way.

- Josef

Re: #1 DevCPT bug

Posted: Thu Sep 18, 2014 7:51 am
by Bernhard
Josef Templ wrote:I have merged issue-#13 into master.
congratulations.

Although I currently don't have a slightest idea, how it could be automated, we should update the About Panel.

I did it for now by hand and included it as Attachement since I do not (yet) know how to "commit".

It should be but in System/Rsrc/About and the important info is stuffed into an embedded document, which is opened by default in "Mask Mode" (the same as its master doument).

--
Bernhard

Re: #1 DevCPT bug

Posted: Thu Sep 18, 2014 8:28 am
by Ivan Denisov
bernhard wrote:Although I currently don't have a slightest idea, how it could be automated, we should update the About Panel.

I did it for now by hand and included it as Attachement since I do not (yet) know how to "commit".

It should be but in System/Rsrc/About and the important info is stuffed into an embedded document, which is opened by default in "Mask Mode" (the same as its master document).
Bernhard, we are discussing the About dialog here:
http://forum.blackboxframework.org/view ... f=33&t=131
http://redmine.blackboxframework.org/issues/15

You can download trial BlackBox with new About dialog here:
http://blackboxframework.org/unstable/i ... a1.005.zip

Your opinion is important. What do you think about new logo?
Also we need you to join us for asking chair to make voting for About dialog.

Re: #1 DevCPT bug

Posted: Thu Sep 18, 2014 8:33 am
by Josef Templ
> I did it for now by hand and included it as Attachement since I do not (yet) know how to "commit".

Bernhard, there is already an issue for updating the About dialog.
It is issue-#15 in the cleaned up redmine issue tracker.
There is also a topic branch for that topic in the cleaned up blackbox repository on GitHub.
The topic branch is named issue-#15 and contains the changes we have agreed on
while we were using the old (not cleaned up) redmine issue tracker and repository
plus it contains a slightly updated logo and a fix for a small typo.
You can download the changed About dialog from GitHub as a single file System/Rsrc/About.odc.
If you want to look at a downloadable BlackBox version that already includes this change,
look at the development versions download page.
For issue-#15 this is http://blackboxframework.org/unstable/i ... a1.005.zip.
The nice thing about this About dialog is that it adapts itself to changes of the version
or build date. It uses System properties (string resources) for that purpose.

To all center members:
Please have a look at the related Wiki pages that explain the development process in more detail.
http://wiki.blackboxframework.org/index ... g_Strategy
http://wiki.blackboxframework.org/index ... ild_Engine
http://wiki.blackboxframework.org/index ... p_with_Git

- Josef