On Tue, 16 Feb 2016 19:47:37 +1300 Daniel Reurich <[email protected]> wrote:
> On 16 February 2016 3:35:55 PM NZDT, Steve Litt > <[email protected]> wrote: > >When a version is a release, don't you just give it a tag? > > > Yes. But that is no excuse for not using private branches to develop > on. If you have to revert a commit your probably doing it wrong. > Please keep master branches for merging tested and release ready > branches only. > > For Devuan packaging projects, devuan/<release> branches should be > marked protected and changes proposed via merge requests. And the > owners/masters should be the only ones to merge changes and set > release tags. > > Daniel Thanks for the clarification Daniel. Should each developer create a branch for each of his/her subprojects? Or a branch for each subproject? Or a single development project to merge into Master on the rare occasion when the development branch is functioning and tested? Thanks, SteveT Steve Litt February 2016 featured book: The Key to Everyday Excellence http://www.troubleshooters.com/key _______________________________________________ Dng mailing list [email protected] https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
