Bigtop is hosted on git-wip-us and force pushes are disallowed. I've asked on the INFRA JIRA if it is a global policy for git-wip-us or could be changed on a per project basis but I also believe we should rewrite history only in rare cases. Also based on observing Bigtop's use of Apache git hosting, If one of us does accidentally push up toxic waste, we can create a temporary branch that is the fixed version of the broken branch, and involve infra to clean up the mess. Presumably those communications would be copied to dev@ so everyone knows a rewrite is coming and can take steps.
On Wed, May 21, 2014 at 11:17 AM, Stack <[email protected]> wrote: > Migration is almost done. Next up will be verifying all made it over. > Till then GIT is read-only. See the INFRA issue for status. > > > On Wed, May 21, 2014 at 10:19 AM, Nick Dimiduk <[email protected]> wrote: > > > Is there a resolution published somewhere? Do we have any ground rules > for > > making effective use of git? For instance, if we want to maintain linear > > histories, we should enforce fast-forward only pushes. Do we allow forced > > pushes to published branches? What about policies for feature branches -- > > should these preserve history? Will we squish the feature into a single > > commit? &c. > > > > Git is very nice, but also gives us more rope than we had before. > > > > > Agreed. > > Lets try and hold to linear histories and our current practice version > branching (as suggested over in the DISCUSSION thread by a few our our dev > crew). On feature branches, lets see. Squash if messy history (most > cases?)? > > The Accumulo doc makes for a good start [1] (ignoring where their branching > style is different to ours). It is informed by the Kafka contributors > workflow doc, also a good read [2]. When in doubt, do as we've done in the > past: e.g. adding patch to JIRA for hadoopqa run. Dump dev pains and > suggested solutions into this thread. Lets keep this thread alive with > issues we run into as a dev team and our (suggested) solutions. As our > practice diverges from that outline in docs above, lets note and add doc > locally? > > I need to heads-up our FB brothers and sisters too.... > > St.Ack > > 1. http://accumulo.apache.org/git.html > 2. > > https://cwiki.apache.org/confluence/display/KAFKA/Patch+submission+and+review#Patchsubmissionandreview-Simplecontributorworkflow > > > > > > Perhaps this has some useful formulae: > > > http://git-scm.com/book/en/Customizing-Git-An-Example-Git-Enforced-Policy > > > > > > On Tue, May 20, 2014 at 10:10 PM, Talat Uyarer <[email protected]> wrote: > > > > > Good news :) > > > 21 May 2014 08:05 tarihinde "Stack" <[email protected]> yazdı: > > > > > > > SVN has been flipped read-only. The migration to git has started. > See > > > > https://issues.apache.org/jira/browse/INFRA-7768 > > > > > > > > St.Ack > > > > > > > > > > > > On Mon, May 19, 2014 at 3:56 PM, Stack <[email protected]> wrote: > > > > > > > > > On Mon, May 19, 2014 at 1:48 PM, Talat Uyarer <[email protected]> > > > wrote: > > > > > > > > > >> Hi All, > > > > >> > > > > >> I created an issue for our git migrating. [0] We can follow our > > > > >> migration status. Fyi > > > > >> > > > > > > > > > > Thank you Talat, > > > > > St.Ack > > > > > > > > > > > > > > > -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
