I don't want to sway this discussion one way or another, so I will just make a data point (or perhaps a helpful hint ;)
In Bigtop (and in some other projects I've partaken/observed) the content of the release would be discussed either on the dev@ list or in a special JIRA. One such example would be an ongoing BIGTOP-2282 or already completed BIGTOP-2078. This way an RM can always gauge the level of interest for different features and make an educated guess on when to cut an RC. Cos On Fri, Mar 04, 2016 at 03:47PM, moon soo Lee wrote: > Hi folks, > > Zeppelin project used made releases driven by feature. > I'm getting constant feedback from users about moving to date-driven > release policy from current feature-driven. (such as major release every 3 > months) > > They have pros and cons. The question is, which policy is better for users > and developers of this project? > > One good thing about date driven approach i think is, Zeppelin usually gets > a lot of contributions not in the release scope. Date driven policy can > give user expectation of availability of those contributions. > > What do you think? Can you share your experiences and opinions? > > Thanks, > moon
signature.asc
Description: Digital signature
