Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Plain View
Accumulo >> mail # dev >> GIT


+
Christopher 2013-05-21, 21:44
+
John Vines 2013-05-21, 21:51
+
Corey Nolet 2013-05-21, 22:06
+
David Medinets 2013-05-21, 22:05
+
Christopher 2013-05-21, 22:12
+
Benson Margulies 2013-05-21, 22:25
+
Mike Drob 2013-05-21, 22:25
+
Mattmann, Chris A 2013-05-21, 22:28
+
Benson Margulies 2013-05-21, 22:29
+
Michael Wall 2013-05-21, 23:32
+
Keith Turner 2013-05-22, 14:32
+
Billie Rinaldi 2013-05-22, 14:40
+
Josh Elser 2013-05-22, 14:57
+
David Medinets 2013-05-23, 00:42
+
John Vines 2013-05-23, 00:47
+
Jason Trost 2013-05-23, 12:23
+
Josh Elser 2013-05-23, 13:08
+
Christopher 2013-05-23, 15:40
+
David Medinets 2013-05-23, 18:02
+
Jason Trost 2013-05-26, 18:54
+
Billie Rinaldi 2013-05-26, 19:15
+
David Medinets 2013-05-22, 00:25
+
Josh Elser 2013-05-21, 22:27
+
Christopher 2013-06-01, 20:28
+
Jason Trost 2013-06-02, 17:54
+
Josh Elser 2013-06-04, 13:07
+
Drew Farris 2013-06-05, 02:05
+
Benson Margulies 2013-06-05, 02:24
+
Josh Elser 2013-06-05, 02:16
+
Benson Margulies 2013-06-05, 02:26
+
Sean Busbey 2013-06-05, 02:46
+
Christopher 2013-06-05, 03:35
+
Josh Elser 2013-06-05, 02:49
On Tue, Jun 4, 2013 at 10:49 PM, Josh Elser <[EMAIL PROTECTED]> wrote:

>
> On 06/04/2013 10:26 PM, Benson Margulies wrote:
>
>> 1.4.4 has been released. The first person finds some changes that should
>>> be
>>> placed into a 1.4.5 release. As such, a 1.4.5-SNAPSHOT branch would be
>>> created from the 1.4.4 tag.
>>>
>> What's the advantage of 1.4.5-SNAPSHOT as opposed to a branch named
>> 1.4.x? On other projects, there's an assumption of one branch per
>> maintained minor version, with point releases as tags along they way.
>> How is your more complex? scheme advantageous?
>>
> Much of this discussion is entirely based on the fact that my opinions
> were solicited while the majority of people tended not to agree with how I
> would prefer to manage branches.
>
> As such, I've stopped arguing my points as, and will attempt to be
> detached.  Having been part of transition a decent-sized "subversion" team
> to git, which typically tries to manage with 2+ concurrent releases, I've
> developed my own opinions on how to manage this. Most of it stems from lack
> of moderation on where changes should be made in such an environment and
> that history is easily mucked up and when changes are placed in
> inappropriate places. If it seems completely absurd to even have this
> discussion (I don't fault you in the slightest -- I'm 99% there myself),
> I'm actively working a write-up to track concrete decisions.
>

Can you give more detail about "history is easily mucked up"?  I am curious
what constitutes a mucked up history and what sequence of steps lead to
this?
>
> As far as a minor-release branch name, I really just don't care. It's a
> name. My opinion is to tie it to something specific and meaningful. I do
> not find 1.4.x nomenclature meaningful, so, as such, I proposed
> alternatives.
>
> Ultimately, I hope that those currently performing the most development
> should form their own opinion from the facts that have been presented when
> it comes time for a decision to be made.
>
+
Josh Elser 2013-06-05, 13:16
+
Keith Turner 2013-06-05, 14:51
+
Josh Elser 2013-06-05, 16:23
+
Christopher 2013-06-05, 16:29
+
Billie Rinaldi 2013-06-05, 16:48
+
Christopher 2013-06-05, 17:07
+
Aaron G 2013-06-04, 13:41
+
Josh Elser 2013-06-04, 14:04
+
Aaron G 2013-06-04, 14:09
+
Keith Turner 2013-06-04, 13:35
+
Josh Elser 2013-06-04, 14:01
+
Keith Turner 2013-06-04, 21:51
+
Christopher 2013-06-04, 22:09
+
Christopher 2013-06-04, 22:11
+
David Medinets 2013-06-04, 22:27
+
Billie Rinaldi 2013-06-05, 12:17
+
David Medinets 2013-06-05, 16:49
+
Christopher 2013-06-05, 16:59
+
Christopher 2013-06-04, 18:34
+
Joe Stein 2013-06-04, 18:39
+
Drew Farris 2013-06-05, 01:37
+
Josh Elser 2013-06-04, 20:15
+
Christopher 2013-06-04, 21:05
+
Josh Elser 2013-06-14, 01:41