On 06/08/17 22:40 , David Anderson wrote:
> Testing a feature in isolation is not the same as testing the system.
True.
> No one is advocating committing untested or buggy code into master.
Yet it happens most of the time, mostly because *development* happens in
master. And even if one sees a se
On 2017-08-06 22:40, David Anderson wrote:
Please read https://boinc.berkeley.edu/trac/wiki/SoftwareTesting
in particular the definition of "stable".
[...]
Testing a feature in isolation is not the same as testing the system.
Indeed.
But that doesn't mean that "testing in isolation" shouldn'
Thanks for that last paragraph, Oliver. You put into words what has been
running through my mind since Friday.
-- Jord van der Elst.
On Mon, Aug 7, 2017 at 9:55 AM, Oliver Bock wrote:
> On 06/08/17 22:40 , David Anderson wrote:
> > Testing a feature in isolation is not the same as testing the
Well, git makes one's "senses reeling", at least when one has started a
career with CVS. Linus had helped us escape, and he possibly gets more
respect from me for that than for his kernel work. For me, it was the
git repository for BOINC _packaging_ that had forced me into it, long
before BOINC tra
On 07.08.2017 16:21, Steffen Möller wrote:
> So, please find a way to stop this so very outdated discussion.
This discussion is meant to help reaching a consensus on how to do
things in the future - the very things you asked for. Only when one
established the how one can establish the who.
> Heck
Steffen:
I agree - git is here to serve us, not vice versa :-)
I've proposed creating server release branches,
similar to the exiting client release branches.
Hopefully this will satisfy everyone's needs.
-- David
On 8/7/2017 7:21 AM, Steffen Möller wrote:
Well, git makes one's "senses reeling
HI Oliver,
On 07/08/17 09:55, Oliver Bock wrote:
As Laurence pointed out: release branches are to stabilize
and fix releases.
This is not what I intended to communicate. When the master (which
should be stable) has the required features and been tested, a release
is made and a branch versi
Please read https://boinc.berkeley.edu/trac/wiki/SoftwareTesting
-- David
On 8/4/2017 3:38 PM, Laurence Field wrote:
Hi David,
On 04/08/17 23:17, David Anderson wrote:
It's simple:
1) fork master, e.g. to client_release_xxx. It's not stable at this point.
2) test client_release_xxx (e.g. us
Hello,
On 07.08.17 21:40, David Anderson wrote:
> Steffen:
> I agree - git is here to serve us, not vice versa :-)
;) I just removed a story on why people introduce
software like SAP in a company that has not seen
proper controlling before. Too much text.
> I've proposed creating server release b
On 8/7/2017 5:20 PM, Steffen Möller wrote:
No. It won't it is very much off the problem. Offer
separate repositories ( as in github.com/BOINC/client
and github.com/BOINC/server, not branches, and you
make people happier. Of course the two repositories
have zero code redundancy.
Perhaps you hav
On 07.08.17 21:40, David Anderson wrote:
I've proposed creating server release branches,
similar to the exiting client release branches.
Hopefully this will satisfy everyone's needs.
What I (and others) need is a "stable" branch (whatever named) I can
- branch off my own development to work wit
Outside view. The misunderstandings appear to originate in the purpose of GiT
in the first place:
- CVS/SVN --> Forking is bad, Don;t fork, Head is for active development, tags
for snapshots, branching is like theft. Dilution of the developer base
- Git --> Forking is good, fork and fork ofte
Please read
https://boinc.berkeley.edu/trac/wiki/SoftwareTesting
-- David
On 8/7/2017 10:28 PM, Bernd Machenschalk wrote:
On 07.08.17 21:40, David Anderson wrote:
I've proposed creating server release branches,
similar to the exiting client release branches.
Hopefully this will satisfy everyone
On 2017-08-08 08:23, David Anderson wrote:
Please read
https://boinc.berkeley.edu/trac/wiki/SoftwareTesting
Yes, I did a number of times.
What exactly are you referring to?
- I am referring to development in BOINC in general, not restricted to
the server software.
- The fact that you don't
14 matches
Mail list logo
