At Polygene we referred to this article; http://nvie.com/posts/a-successful-git-branching-model/ and borrowed the nice graphics to our page. The one on http://plc4x.apache.org/developers/contributing.html is impossible for me to see, probably because of colors and not enough contrast, but also too small.
Cheers Niclas On Sun, Nov 18, 2018 at 4:20 PM Christofer Dutz <christofer.d...@c-ware.de> wrote: > Ok … > > So it seems the branch and version updates worked nicely. > I just pushed some documentation update and this should be available in > the website soon. > I added some documentation to the Contributing page (started filling this > with content: http://plc4x.apache.org/developers/contributing.html) > And I added some documentation to the release documentation: > http://plc4x.apache.org/developers/release.html > But as I mentioned … could be a few minutes till the website is updated. > > Chris > > Von: Otto Fowler <ottobackwa...@gmail.com> > Datum: Mittwoch, 14. November 2018 um 15:55 > An: "dev@plc4x.apache.org" <dev@plc4x.apache.org>, Christofer Dutz < > christofer.d...@c-ware.de> > Betreff: Re: [WARNING] Please don't commit anything to `master` effective > immediately > > Have you written up something in confluence and in the root of the source > dir that documents the branching strategy? > > > > On November 14, 2018 at 07:59:11, Christofer Dutz ( > christofer.d...@c-ware.de<mailto:christofer.d...@c-ware.de>) wrote: > Hi all, > > I just thought I‘d post this as a reminder. I am currently in the process > of creating the new `develop` branch and currently adjusting the build > scripts do what they did for master for develop now. > > From now on, the only commits done to master should be the release manager > merging the latest release version back to master after a successful > release. > > Commits to master will cause a lot of problems from now on. > > Chris > -- Niclas Hedhman, Software Developer http://polygene.apache.org - New Energy for Java
