[LRUG] Git Common-Flow (1.0.0-rc.3)

[Sasha Gerrand]

Most of your proposal seems reasonable to me. It certainly follows my
preferred way of working.

One piece of feedback for you: the section on "Releases" seems onerous to
me, but it appears that the intent of the formatting aspect of this part of
your specification is orientated towards machine processing.

On 24 July 2017 at 17:01, Jim Myhrberg <contact at jimeh.me> wrote:

> Hey everyone, I've been lurking on this mailing list for years and rarely
> say much of anything, but I figure people here might appreciate this:
>
> https://commonflow.org/
>
> In short it's "an attempt to gather a sensible selection of the most
> common usage patterns of git into a single and concise specification."
>
> My original goal was to make it easy to adapt a simple and easy workflow
> within organizations that typically want/need things specified, and simply
> saying "just use GitHub Flow and add release tags" wasn't good enough. I
> might have taken things a bit to the extreme, but hopefully the end result
> is something good and useful to others too.
>
> I would really appreciate feedback, both good and bad. Since the spec is
> still in the release candidate phase, I'm hoping to get some valuable
> feedback from outside of my circle of friends before a official 1.0.0
> release.
>
> Thanks for everyone's time :)
>
>
> _______________________________________________
> Chat mailing list
> Chat at lists.lrug.org
> Archives: http://lists.lrug.org/pipermail/chat-lrug.org
> Manage your subscription: http://lists.lrug.org/options.cgi/chat-lrug.org
> List info: http://lists.lrug.org/listinfo.cgi/chat-lrug.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lrug.org/pipermail/chat-lrug.org/attachments/20170725/46a7665a/attachment-0002.html>