On Fri, May 1, 2015 at 6:53 AM, Anthony Baker wrote:
> I suggest we adopt the gitflow model for branching as described in [1] and
> [2]. Following an established and consistent pattern for branching makes
> it easier for new users and devs to contribute.
>
+1
Should we also standardize on using
On Fri, May 1, 2015 at 7:07 AM, jan i wrote:
> On 1 May 2015 at 15:53, Anthony Baker wrote:
>
> > I suggest we adopt the gitflow model for branching as described in [1]
> and
> > [2]. Following an established and consistent pattern for branching makes
> > it easier for new users and devs to con
On 1 May 2015 at 15:53, Anthony Baker wrote:
> I suggest we adopt the gitflow model for branching as described in [1] and
> [2]. Following an established and consistent pattern for branching makes
> it easier for new users and devs to contribute.
>
> Here are the main gitflow concepts:
>
> 1) Th
Hi
I would like to ask the community, how is Mentors viewed in this project ?
- Are we (just) external advisers, that basically check/inform the apache
project about the apache way.
or
- Are we part of the project, and expected to participate in
discussions/votes etc.
I am happy with both roles
I suggest we adopt the gitflow model for branching as described in [1] and [2].
Following an established and consistent pattern for branching makes it easier
for new users and devs to contribute.
Here are the main gitflow concepts:
1) The master branch is reserved for production-ready code, ak
