Comments (5)
I agree with you. @aculich and I configured the repo this way with more
activity in mind I think it is overdesigned for the amount of activity we
have. (though the degree to which dev trails master is just my being lazy)
Aaron, thoughts?
Ryan
On Wed, Jul 15, 2015 at 9:27 PM, Chris Kennedy [email protected]
wrote:
I think focusing on the master branch for bug fixes and new features would
be a better model git workflow for this project, particularly given that
the modification velocity is somewhat sporadic. It doesn't seem to me that
the overhead of a separate dev branch is beneficial for the circumstances
of this project. Under the current policy "dev" is the useful branch and
"master" is generally out of date, plus there isn't a big userbase that is
building from master for whom we need to carefully guard against the minor
chance of bugs creeping in.Right now master is 72 commits behind dev and master hasn't been updated
in 6 months. I would argue that under the BCE use case (single digit usage
of the source repo, 99% of users are only downloading the generated .ovas
or using the AMIs) there is not really a benefit to holding "production"
from all of the improvements that have been made since January.Here are a few related articles that I reviewed as food for thought:
- http://blog.endpoint.com/2014/05/git-workflows-that-work.html
- http://www.barryodonovan.com/2012/07/03/two-git-branching-models
- http://nvie.com/posts/a-successful-git-branching-model/
As one proof of concept, Caret is the main machine learning framework in R
that does this with a much larger source userbase:
https://github.com/topepo/caretSo I would like to put in a vote to remove the "dev" branch approach in
favor of simply merging directly to master.—
Reply to this email directly or view it on GitHub
#50.
from bce.
I'm in favor of simplifications that make managing it easier.
from bce.
A quote I like from the first article is:
Complicated workflows drive people crazy. Make it simple. Review your workflow and ask how you can simplify it. In actively making things more simple, you will also make them easier to understand and work with as well as easier for others to adopt and maintain.
A master-only workflow is fine with me for the amount of activity the repo has.
from bce.
In the meantime at least I've set "dev" as our default branch on github, which I think will be helpful.
from bce.
Ok, I merged dev onto master and made master the default branch.
from bce.
Related Issues (20)
- download speeds can be _very_ slow in BCE HOT 4
- Add support for network manager to connect to campus VPN HOT 3
- NFS fails in summer-2015 when launching Starcluster clusters HOT 4
- summer-2015 EC2 image lacking python packages HOT 4
- BCE HackDay HOT 6
- some issues in the build scripts to address for fall-2015 HOT 1
- make sure Python links against openBLAS HOT 3
- enable byobu by default for cloud images
- change default Vbox user to be ubuntu HOT 3
- parallel python tools to consider HOT 1
- remove old BCE AMIs HOT 1
- Reorganize BCE files on shared folders HOT 7
- Can't serve files from shared folders on apache HOT 1
- ixgbevf networking driver version update
- Add extensive updates to setup_ipython_notebook.sh HOT 2
- Evaluate basing BCE on existing Docker stack HOT 1
- build on cfncluster 16.04 LTS release once it is available for AWS HOT 3
- move Miniconda install to /opt
- clean up packer .json and bootstrap scripts for docker build in docker branch
- add tidyverse (or at least readr) R packages to next release
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from bce.