Hi All, I have some comments on the repository structure and most of them are wrt my experience in another Apache incubating project.
1. Most active projects use *master* as default development branch than *develop*. For example, Flink, Spark, Storm, Samza, Pig, Hive, and Hadoop use master branch. 2. Released artifacts are always hosted on downloads page.Maser need not be the one with production ready state. 3. It is quite intuitive to use *master* otherwise new contributors needs to go through documentation to understand process of each project. 4. Overall, the process becomes simple if *master* is the default branch. Another suggestion is related to release with major version change. Major release twice a year is a lot of burden on the end user if they want to upgrade to a newer version. To address this issue, newly added APIs can be marked as @evolving so that users are aware of possible change in the upcoming release but the stable one should be carefully changed. Regards, Sandeep On Sat, Feb 13, 2016 at 2:34 AM, Frances Perry <[email protected]> wrote: > Thanks for all the feedback! Please keep it coming as needed. > > We've gone ahead and created components matching this structure: > > https://issues.apache.org/jira/browse/BEAM/?selectedTab=com.atlassian.jira.jira-projects-plugin:components-panel > > We'll work on transition existing state from Google-internal tools into > this over the next few weeks. > > > On Fri, Feb 12, 2016 at 7:47 AM, Kenneth Knowles <[email protected]> > wrote: > > > On Thu, Feb 11, 2016 at 8:53 AM, Maximilian Michels <[email protected]> > > wrote: > > > > > As for the /develop branch, I would suggest to > > > make it mandatory to have it in a usable state at all times. > > > > > > > +1 > > > > If breakage is accidentally committed (as will happen) then a CTR > rollback > > is a encouraged. > > > > Kenn > > >
