I'd not adopt gitflow in this project, after all sooner than api should be become stable enough for having small activity at master.
On Fri, May 8, 2015 at 3:23 PM, Stian Soiland-Reyes <[email protected]> wrote: > Thanks for joining! > > So you suggest the git model where master would be at the latest > non-patch release? (why not just the latest release?) > > Not too far off from > http://nvie.com/posts/a-successful-git-branching-model/ > > But I think this could be confusing to GitHub users who want to > contribute with pull requests.. at least during this incubation phase > where we are open for larger change. > > > On 7 May 2015 at 18:13, Jakob Frank <[email protected]> wrote: > > Hi all, > > > > finally after all this BNode discussion something simple where to start > > contributing ;-) > > > > Am 07.05.2015 16:39 schrieb "Sergio Fernández" <[email protected]>: > >> > >> Keeping the api as priority, maybe we can have the rule that master will > >> always contain X.Y.0-SNAPSHOT version. After all X.Y.Z are maintenance > >> versions we can keep on their on branch. > > My suggestion would be to have master on X.Y.0 (no snapshot), and the > > develop branch for the X.Y+1.0-SNAPSHOT to evolve the API. > > The X.Y.1 versions should stay on their maintenance branches. > > > > Best, > > Jakob > > > >> But I think we should discuss that aspect. That for bring it in, Stian. > >> > >> Cheers, > >> > >> > >> -- > >> Sergio Fernández > >> Partner Technology Manager > >> Redlink GmbH > >> m: +43 6602747925 > >> e: [email protected] > >> w: http://redlink.co > > > > -- > Stian Soiland-Reyes > Apache Taverna (incubating), Apache Commons RDF (incubating) > http://orcid.org/0000-0001-9842-9718 > -- Sergio Fernández Partner Technology Manager Redlink GmbH m: +43 6602747925 e: [email protected] w: http://redlink.co
