On Fri, Apr 23, 2010 at 9:57 AM, Lars Francke wrote:
>> Speaking of 'mvn site', it would be awesome if it didn't take ~40
>> minutes to run.
>
> The "problem" is that the site runs the tests again (intentionally).
Sorry, I forgot to mention I actually ran:
$ MAVEN_OPTS=-Xmx512m mvn site -DskipT
For the sake of tracking this - HBASE-2484 in place.
On Fri, Apr 23, 2010 at 12:46 AM, Andrew Purtell wrote:
> I like it also. It's appropriate.
>
> - Andy
>
> > From: Ryan Rawson
> >
> > I am somewhat interested in this :-)
> >
> > But it can make life difficult for our users... thoughts
> >
> Speaking of 'mvn site', it would be awesome if it didn't take ~40
> minutes to run.
The "problem" is that the site runs the tests again (intentionally).
Cobertura has the philosophy that the tests should run once
uninstrumented and once more instrumented for coverage data to be sure
that possibl
On Fri, Apr 23, 2010 at 1:45 AM, Lars Francke wrote:
> I will spend some time on the Maven site then. Shouldn't be too hard
> to at least get a basic site up but this being Maven
Speaking of 'mvn site', it would be awesome if it didn't take ~40
minutes to run.
And for the records, the API do
> Lets do a revamp on website while we're moving stuff around. We
> should make maven site work but that the generated maven site
> index.html shouldn't be our front page (unless someone knows how to
> super style the maven generation). I'd think front page should be
> nice and clean that links t
I would declare 1.0 after:
- Data durability guarantees (0.20.5 post)
- Master rewrite (0.21 post)
- No more region state transition holes
- No more double assignments (use ZK to assure against)
- Distributed log splitting
- Tighten up splits and compactions, and failure
Since you're asking, IMHO, it's minimally confusing to have the next minor
relase be 0.20.5, the next major release be 0.21, and the release after be 1.0,
with all that entails.
- Andy
> From: Stack
> Subject: Re: HBase move to Apache Top Level Project
>
> So, the new
Sounds good to me. So how about doing another hackathon next month? My plan for
May is to be up in the area for ~8 days over the month because I'll be around
the world for 5 weeks straight after.
- Andy
> From: Todd Lipcon
[...]
> it would be nice to have a hackathon day where
> we force ours
: Dhruba Borthakur [mailto:dhr...@gmail.com]
> > Sent: Friday, April 23, 2010 12:37 AM
> > To: hbase-dev@hadoop.apache.org
> > Subject: Re: HBase move to Apache Top Level Project
> >
> > I think it is too early to cal the next impending 0.20.5 release to be
> > the
&
I like it also. It's appropriate.
- Andy
> From: Ryan Rawson
>
> I am somewhat interested in this :-)
>
> But it can make life difficult for our users... thoughts
> people?
>
> On Thu, Apr 22, 2010 at 11:17 PM, Karthik K wrote:
> >
> > This is great news. Congrats HBase team.
> >
> > (Does t
e nice for 1.0 as well.
> -Original Message-
> From: Dhruba Borthakur [mailto:dhr...@gmail.com]
> Sent: Friday, April 23, 2010 12:37 AM
> To: hbase-dev@hadoop.apache.org
> Subject: Re: HBase move to Apache Top Level Project
>
> I think it is too early to cal the next
; date and so might be worthy of new shiny versioning/packaging as a TLP.
>> >> Website/docs/wiki refresher to boot.
>> >> >
>> >> > Changing the package names is way more invasive to client code but I'm
>> >> always +1 on making stuff shorte
cated.
> >>
> >> St.Ack
> >>
> >> >
> >> >
> >> > Anyways, I'm not doing much production cluster maintenance these days
> so
> >> these changes would impact me way less than others. Will welcome
> pushback
> >> if
p.apache.org
> Subject: Re: HBase move to Apache Top Level Project
>
> When do we want to declare a 1.0? When we are running on HDFS-265?
> When we run on a hdfs that doesnt lose data?
>
> If the latter, then 0.20.5 is a contender. There is a lot of
> expectation out of a 1.0.
&
nd the old stuff deprecated.
>>
>> St.Ack
>>
>> >
>> >
>> > Anyways, I'm not doing much production cluster maintenance these days so
>> these changes would impact me way less than others. Will welcome pushback
>> if you guys don't want to deal wi
;m not doing much production cluster maintenance these days so
> these changes would impact me way less than others. Will welcome pushback
> if you guys don't want to deal with this.
> >
> > JG
> >
> >> -Original Message-
> >> From: Ryan Rawson [mail
ter.
>> >
>> >
>> > Anyways, I'm not doing much production cluster maintenance these days so
>> these changes would impact me way less than others. Will welcome pushback
>> if you guys don't want to deal with this.
>> >
>> > JG
>>
ion cluster maintenance these days so
> these changes would impact me way less than others. Will welcome pushback if
> you guys don't want to deal with this.
>
> JG
>
>> -Original Message-
>> From: Ryan Rawson [mailto:ryano...@gmail.com]
>> Sent: Thursda
come pushback
> if you guys don't want to deal with this.
> >
> > JG
> >
> >> -Original Message-
> >> From: Ryan Rawson [mailto:ryano...@gmail.com]
> >> Sent: Thursday, April 22, 2010 11:20 PM
> >> To: hbase-dev@hadoop.apache.org
d impact me way less than others. Will welcome pushback if
> you guys don't want to deal with this.
>
> JG
>
>> -Original Message-
>> From: Ryan Rawson [mailto:ryano...@gmail.com]
>> Sent: Thursday, April 22, 2010 11:20 PM
>> To: hbase-dev@hadoop.apache.org
JG
> -Original Message-
> From: Ryan Rawson [mailto:ryano...@gmail.com]
> Sent: Thursday, April 22, 2010 11:20 PM
> To: hbase-dev@hadoop.apache.org
> Subject: Re: HBase move to Apache Top Level Project
>
> I am somewhat interested in this :-)
>
> But it can make l
I've started working with a pro designer and I'll let you all know if
it goes anywhere.
On Thu, Apr 22, 2010 at 11:29 PM, Stack wrote:
> Will make patching branch and trunk even harder than it already is w/
> the maven repositioning but I'm +1. o.a.h is neat and tidy compared
> to o.a.h.h.
>
> L
Will make patching branch and trunk even harder than it already is w/
the maven repositioning but I'm +1. o.a.h is neat and tidy compared
to o.a.h.h.
Lets do a revamp on website while we're moving stuff around. We
should make maven site work but that the generated maven site
index.html shouldn't
I am somewhat interested in this :-)
But it can make life difficult for our users... thoughts people?
On Thu, Apr 22, 2010 at 11:17 PM, Karthik K wrote:
> This is great news. Congrats HBase team.
>
> (Does this mean, the packages would be refactored as o.a.hbase.* in the
> trunk ? ).
>
> --
> K
This is great news. Congrats HBase team.
(Does this mean, the packages would be refactored as o.a.hbase.* in the
trunk ? ).
--
Karthik.
On Thu, Apr 22, 2010 at 10:47 PM, Cosmin Lehene wrote:
> This is great news!
>
> On Apr 22, 2010, at 8:32 PM, Stack wrote:
>
> > The board yesterday passed
This is great news!
On Apr 22, 2010, at 8:32 PM, Stack wrote:
> The board yesterday passed a resolution making HBase a TLP.
>
> I filed an infrastructure issue to start the move:
>
> https://issues.apache.org/jira/browse/INFRA-2641
>
> The primary disruption to developers will be when the sub
+1 on moving to read-write Git.
Maybe there will be that miracle and/or we have some more input than before.
- Andy
A lot of things in wiki should be in the site itself. Perhaps during a site
redesign
On Apr 22, 2010 12:00 PM, "Stack" wrote:
On Thu, Apr 22, 2010 at 11:25 AM, tsuna wrote:
> On Thu, Apr 22, 2010 at 10:32 ...
Yes
>> developers can use 'svn switch' to update their repos (There is no
>> ap
On Thu, Apr 22, 2010 at 11:25 AM, tsuna wrote:
> On Thu, Apr 22, 2010 at 10:32 AM, Stack wrote:
>> The primary disruption to developers will be when the subversion
>> repository is renamed. We'll send out a note before we do this, then
>
> Technically, I don't think the repository gets renamed.
On Thu, Apr 22, 2010 at 10:32 AM, Stack wrote:
> The primary disruption to developers will be when the subversion
> repository is renamed. We'll send out a note before we do this, then
Technically, I don't think the repository gets renamed. It's just a
matter of moving a directory in the tree w
30 matches
Mail list logo
