Congrats on the move to Git. I've been watching this particular email thread with a little confusion.
On GitHub, I believe it is expected to submit a pull request for any non-trivial change. It seems reasonable to me that, if the history of a pull request deserves squashing before being merged, just ask people to do that. And if they don't know, point them at a page that tells them how. That works for all the people who are not committers on the project. The only remaining problem is just getting committers to agree on what to do. Seems like you can follow the same process - fork on GitHub for significant changes, do a pull request for merging back. On Fri, May 19, 2017 at 9:18 AM, Gary Gregory <[email protected]> wrote: > On May 19, 2017 6:14 AM, "Julian Sedding" <[email protected]> wrote: > > Hi Oleg > > As I explained in the thread branched from this one, I fear that > rewriting public history will irritate/alienate potential contributors > as well as existing committers. > > In my opinion deterring contributors is a hefty price to pay in order > to satisfy your desire for an immaculate public history. > > As I understand it, you "need" the clean public history in order to > create the release notes. Is that correct? > > I suggested to base the release notes on JIRA issues instead. Is this > not possible? If yes, why? > > > There is a maven plugin for that. > > Gary > > > We can already fully control if a PR is merged or not, so we are only > talking about committers spoiling the history. I believe we should be > able to encourage and teach a relatively small group of people to > improve their habits. Your threat of a veto suggests that you are more > pessimistic about this, which makes me sad, especially should you be > right. > > My strong preference is to trust the circle of committers instead of > rewriting public history. > > Regards > Julian > > > > On Fri, May 19, 2017 at 2:59 PM, Oleg Kalnichevski <[email protected]> > wrote: > > On Fri, 2017-05-19 at 13:19 +0200, Michael Osipov wrote: > >> Since I haven't received anymore comments on the guidelines, I'll > >> close > >> the questioning and call a vote for commmitters and PMC members. > >> > >> Michael > >> > > > > Michael > > > > I just want to tell you upfront I will vote -1 on the proposal as long > > as it has the clause about never rewriting release branches. > > > > Oleg > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
