1. commits and tickets
- Posted by SDPringle Jan 25, 2015
- 1415 views
Although there is the popular notion of release early and often, this doesn't really apply to commits. People would rather not have bugs get into the work they are working on, so we end up with Euphoria branching into many branches. In spite of this attitude, I sometimes break things for other people. What is more, what might work fine in Windows might break the interpreter build in Linux or vice versa.
Now if all commits left nothing broken, we could combine hg bisect feature with eutest to find obscure regressions start which were not tested for before. So, it would be nice to go back and change the commit messages of a stream and also, to mark commits as linux-32-tests-well, windows-64-tests-well. Then, have a bisect feature that looks at these flags and skips over those that don't test well.
It is really cool that we have a bot watching the commits and updating the tickets on the fly like this. Now, tickets themselves should have OS-platform flags. I am talking about checkboxes for each OS/platform combination. Testers could flag their platform on a given ticket to signal the problem also exists elsewhere. So, we could filter OSes we don't use when looking at the tickets.
This could be the start of a next generation revision system written in Euphoria working on top of mercurial for example. Now, the implementation is an exercise for the reader. ;)
Shawn
2. Re: commits and tickets
- Posted by jimcbrown (admin) Jan 25, 2015
- 1350 views
Although there is the popular notion of release early and often, this doesn't really apply to commits. People would rather not have bugs get into the work they are working on, so we end up with Euphoria branching into many branches.
Not me. I am quite happy to commit breakage into default or 4.0, myself. 
In spite of this attitude, I sometimes break things for other people. What is more, what might work fine in Windows might break the interpreter build in Linux or vice versa.
I think this is natural and should be accepted. It's not realistic to expect every developer to test every feature on every platform - that's one of the reasons why we work in a group.
Now if all commits left nothing broken, we could combine hg bisect feature with eutest to find obscure regressions start which were not tested for before. So, it would be nice to go back and change the commit messages of a stream and also, to mark commits as linux-32-tests-well, windows-64-tests-well. Then, have a bisect feature that looks at these flags and skips over those that don't test well.
In the past, we have an eubins server running on jeremy's systems and unkmar's systems that built on two platforms. There was no marking in revision control per say, but a record did exist of which commits built well and past all tests and which broke on which platforms.
We no longer have that infrastructure, though someone did donate money so we could afford to buy a new one: http://openeuphoria.org/forum/m/124356.wc
It is really cool that we have a bot watching the commits and updating the tickets on the fly like this. Now, tickets themselves should have OS-platform flags. I am talking about checkboxes for each OS/platform combination. Testers could flag their platform on a given ticket to signal the problem also exists elsewhere. So, we could filter OSes we don't use when looking at the tickets.
This is easy to add into the ticketing system itself, and it'd be easy enough to update the tickets from the eubins server, if we had one...
