Re: Thoughts about DEVELOPERS.md WAS: [travis-ci - fvwm.git master branch is "protected"]

2016-03-25 Thread Thomas Funk
"Thomas Adam" wrote: > On Fri, Mar 25, 2016 at 12:25:09PM +0100, Thomas Funk wrote: > > I think we should. It's better to have such in the documentation so no > > questions appears anymore ;) > > > > I can add it to the document, no prob. > > I've added a few words about this,

Re: Thoughts about DEVELOPERS.md WAS: [travis-ci - fvwm.git master branch is "protected"]

2016-03-25 Thread Thomas Adam
On Fri, Mar 25, 2016 at 12:25:09PM +0100, Thomas Funk wrote: > I think we should. It's better to have such in the documentation so no > questions appears anymore ;) > > I can add it to the document, no prob. I've added a few words about this, without making this a rule, which hopefully people

Re: Thoughts about DEVELOPERS.md WAS: [travis-ci - fvwm.git master branch is "protected"]

2016-03-25 Thread Thomas Funk
"Thomas Adam" wrote: > On Fri, Mar 25, 2016 at 03:30:03AM +0100, Thomas Funk wrote: > > One point: > > Should we use for development branches a special nomination like > > feature_xy, fix_abc? > > Or only a README which describes the feature/fix? > > I don't think that's

Re: Thoughts about DEVELOPERS.md WAS: [travis-ci - fvwm.git master branch is "protected"]

2016-03-25 Thread Thomas Adam
On Fri, Mar 25, 2016 at 03:30:03AM +0100, Thomas Funk wrote: > One point: > Should we use for development branches a special nomination like feature_xy, > fix_abc? > Or only a README which describes the feature/fix? I don't think that's necessary. Typically, you have this pattern:

Thoughts about DEVELOPERS.md WAS: [travis-ci - fvwm.git master branch is "protected"]

2016-03-24 Thread Thomas Funk
"Thomas Adam" wrote: > I was thinking along the lines of this diff: > > https://github.com/fvwmorg/fvwm/commit/f81b2f4d7412813f12b235d8f1914409da0bbae9.patch > > Which you can view rendered here: > > https://github.com/fvwmorg/fvwm/blob/ta/git-docs/docs/DEVELOPERS.md > > What