Re: Bad Git Commit / Advice?

I'm going to leave master as-is and merge in the PRs into develop that I merged into master. It's unfortunate that master will have a snapshot POM on it, but at least those two branches will be consistent. I won't rush to cut a release now, but I'll read up on the ASF incubator release process

Re: Bad Git Commit / Advice?

yep, master didn't like force-push (results below). You don't like the idea of cutting a 3.2.10 release? I'm hesitating to do a revert because (1) my push onto the master involved 13 commits and it seems like that would require 13 reverts and (2) that leaves the master history really ugly...

Re: Bad Git Commit / Advice?

When y'all say "cutting a 3.2.10 release" do you mean going through the ASF incubator process for having a release? On Dec 22, 2015 16:45, "Aaron D. Mihalik" wrote: > yep, master didn't like force-push (results below). > > You don't like the idea of cutting a 3.2.10

Re: Bad Git Commit / Advice?

Yes-- though I'm not sure how involved that is. Sent from my iPhone > On Dec 22, 2015, at 7:19 PM, Sean Busbey wrote: > > When y'all say "cutting a 3.2.10 release" do you mean going through the ASF > incubator process for having a release? >> On Dec 22, 2015 16:45, "Aaron

Re: Bad Git Commit / Advice?

Haha, that's a good representation of how difficult the first one will be :) Releasing will get that easy -- the first few will not be. I used to try to keep master history "nice", but I've long since given up. I'm convinced that there's no real value in trying to this. You just end up