Well, I got that wrong -- apparently Hive's branch-2.2 is now the same as Owen's. That simplifies things considerably.
So any TODOC2.2 label in Hive's branch-2.2 can be changed to TODOC2.2.0, and then all remaining TODOC2.2 labels can be changed to TODOC2.3. That's a lot easier than examining every JIRA issue. There might be a few recent ones that ought to be TODOC3.0, but we'll catch them as best we can. Corrections, anyone? Since I already muddled part of this, I won't make any global label changes until people have a chance to review my plan. -- Lefty On Wed, Mar 29, 2017 at 1:20 AM, Lefty Leverenz <leftylever...@gmail.com> wrote: > For the upcoming releases, we'll use these TODOC labels in JIRA: > > - *TODOC3.0* for patches committed to master (only) after 23 March > 11:06 pm PST. > - *TODOC2.3* for patches committed to branch-2. > - Patches committed to master *before* 23 March 11:06 pm PST (when > branch-2 was split off) are already labeled *TODOC2.2* but those > labels need to be changed. > - *TODOC2.2.0* for patches committed to Owen's branch-2.2 > <https://github.com/omalley/hive/tree/branch-2.2>, which presumably > will be moved to Hive's github tree eventually *but is not the same as > Hive's branch-2.2 <https://github.com/apache/hive/tree/branch-2.2>*. > > So the old label *TODOC2.2* will become obsolete because it's ambiguous > now that release 2.2.0 is cherry-picking patches made since 2.1.1. > > References: About next 2.3 release > <http://mail-archives.apache.org/mod_mbox/hive-dev/201703.mbox/%3ccams4yue4wn3zabeet-acn6smhup0k8ffgeu3w6m4y9wgjfs...@mail.gmail.com%3e> > , Re: Backward incompatible changes > <http://mail-archives.apache.org/mod_mbox/hive-dev/201703.mbox/%3cCAHfHakEL-+C=q5rnrunxfcmqabnpm5m_h6qrokcrns24cv2...@mail.gmail.com%3e> > . > > Can anyone explain what Hive's branch-2.2 is, and how we're going to avoid > confusing it with Owen's branch-2.2? > > -- Lefty >
