Keith hit me up on chat about this. Turns out for my situation, the code
I'm looking at is still a "bug". Ignore me for now.
For simplicity's sake, hopefully we won't have anything for 1.6.1 that
wouldn't need to go into 1.6.0 as well (only one thing comes to mind).
On 11/22/13, 9:37 PM, Keith Turner wrote:
I was wondering this too.
On Fri, Nov 22, 2013 at 9:25 PM, Sean Busbey <[email protected]>wrote:
Why the 1.6.1-SNAPSHOT prior to 1.6.0 getting released?
On Nov 22, 2013 8:19 PM, "Josh Elser" <[email protected]> wrote:
FYI -- I'll be pushing a 1.6.1-SNAPSHOT branch tonight.
As we finalize things in 1.6.0 that are also in previous versions (bug
fixes), make sure you don't merge 1.5.1-SNAPSHOT directly into
1.6.0-SNAPSHOT anymore. You'll need to merge into 1.6.1-SNAPSHOT and
cherry-pick into 1.6.0-SNAPSHOT (where applicable, of course).
