Re: Post 1.5.3 and 1.6.3
Good point. On Tue, Jul 7, 2015, 15:36 Josh Elser wrote: > Upgrade testing out of 1.5.x to 1.6 or 1.7? > > Christopher wrote: > > What else is there to do for 1.5 EOL? We've indicated this already in > > the 1.5.3 release announcement and we've removed the 1.5 development > > branch. As far as I'm concerned, I think the last remaining thing to > > do is to archive the 1.5 parts of the website... and I see no > > particular rush for that. We can do it along with the next minor or > > major release. > > > > -- > > Christopher L Tubbs II > > http://gravatar.com/ctubbsii > > > > > > On Tue, Jul 7, 2015 at 11:58 AM, Sean Busbey > wrote: > >> I'd like to see the 1.5 EOL happen. > >> > >> On Mon, Jul 6, 2015 at 3:04 PM, Josh Elser > wrote: > >> > >>> Thanks to the efforts spearheaded by Christopher and verified by > everyone > >>> else, we now have 1.5.3 and 1.6.3 releases! > >>> > >>> To keep the ball rolling, what's next? High level questions that come > to > >>> mind... > >>> > >>> * When do we do 1.7.1 and/or 1.8.0? > >>> * What bug-fixes do we have outstanding for 1.7.1? > >>> * What other minor improvements do people want for 1.8.0? > >>> * Where does 2.0.0 stand? Should we make a bigger effort to getting the > >>> new client API stuff Christopher had started into Apache? > >>> > >>> Feel free to brainstorm here and/or on JIRA (tagging relevant issues to > >>> the desired fixVersion) > >>> > >>> - Josh > >>> > >> > >> > >> -- > >> Sean >
Re: Post 1.5.3 and 1.6.3
Upgrade testing out of 1.5.x to 1.6 or 1.7? Christopher wrote: What else is there to do for 1.5 EOL? We've indicated this already in the 1.5.3 release announcement and we've removed the 1.5 development branch. As far as I'm concerned, I think the last remaining thing to do is to archive the 1.5 parts of the website... and I see no particular rush for that. We can do it along with the next minor or major release. -- Christopher L Tubbs II http://gravatar.com/ctubbsii On Tue, Jul 7, 2015 at 11:58 AM, Sean Busbey wrote: I'd like to see the 1.5 EOL happen. On Mon, Jul 6, 2015 at 3:04 PM, Josh Elser wrote: Thanks to the efforts spearheaded by Christopher and verified by everyone else, we now have 1.5.3 and 1.6.3 releases! To keep the ball rolling, what's next? High level questions that come to mind... * When do we do 1.7.1 and/or 1.8.0? * What bug-fixes do we have outstanding for 1.7.1? * What other minor improvements do people want for 1.8.0? * Where does 2.0.0 stand? Should we make a bigger effort to getting the new client API stuff Christopher had started into Apache? Feel free to brainstorm here and/or on JIRA (tagging relevant issues to the desired fixVersion) - Josh -- Sean
Re: Post 1.5.3 and 1.6.3
What else is there to do for 1.5 EOL? We've indicated this already in the 1.5.3 release announcement and we've removed the 1.5 development branch. As far as I'm concerned, I think the last remaining thing to do is to archive the 1.5 parts of the website... and I see no particular rush for that. We can do it along with the next minor or major release. -- Christopher L Tubbs II http://gravatar.com/ctubbsii On Tue, Jul 7, 2015 at 11:58 AM, Sean Busbey wrote: > I'd like to see the 1.5 EOL happen. > > On Mon, Jul 6, 2015 at 3:04 PM, Josh Elser wrote: > >> Thanks to the efforts spearheaded by Christopher and verified by everyone >> else, we now have 1.5.3 and 1.6.3 releases! >> >> To keep the ball rolling, what's next? High level questions that come to >> mind... >> >> * When do we do 1.7.1 and/or 1.8.0? >> * What bug-fixes do we have outstanding for 1.7.1? >> * What other minor improvements do people want for 1.8.0? >> * Where does 2.0.0 stand? Should we make a bigger effort to getting the >> new client API stuff Christopher had started into Apache? >> >> Feel free to brainstorm here and/or on JIRA (tagging relevant issues to >> the desired fixVersion) >> >> - Josh >> > > > > -- > Sean
Re: Separate "Performance Tests" execution documentation
Keith Turner wrote: On Tue, Jul 7, 2015 at 1:48 PM, Josh Elser wrote: I just remembered that Keith made a TESTING.md file I didn't create it, I just renamed it :) $ git log --follow TESTING.md | grep Author Author: Josh Elser Author: Josh Elser Author: Keith Turner Author: Josh Elser Details details, you cleaned it up and pretty-fied it on Github :) https://github.com/apache/accumulo/blob/master/TESTING.md Maybe that would be a logical place? I can add some more Javadoc to the PerformanceTest interface covering how to use it in Java code, but that's probably not a good place to describe how to invoke it. Eric Newton wrote: I would suggest putting it in Javadoc in the PerformanceTest interface. On Tue, Jul 7, 2015 at 12:24 PM, John Vines wrote: README in the top of the testing module? On Tue, Jul 7, 2015 at 12:18 PM Josh Elser wrote: I committed https://issues.apache.org/jira/browse/ACCUMULO-3929 yesterday. Had a thought today that it might be beneficial to write down how it works somewhere, but I don't know where would be best? Any suggestions?
Re: Separate "Performance Tests" execution documentation
On Tue, Jul 7, 2015 at 1:48 PM, Josh Elser wrote: > I just remembered that Keith made a TESTING.md file > I didn't create it, I just renamed it :) $ git log --follow TESTING.md | grep Author Author: Josh Elser Author: Josh Elser Author: Keith Turner Author: Josh Elser > > https://github.com/apache/accumulo/blob/master/TESTING.md > > Maybe that would be a logical place? > > I can add some more Javadoc to the PerformanceTest interface covering how > to use it in Java code, but that's probably not a good place to describe > how to invoke it. > > > Eric Newton wrote: > >> I would suggest putting it in Javadoc in the PerformanceTest interface. >> >> On Tue, Jul 7, 2015 at 12:24 PM, John Vines wrote: >> >> README in the top of the testing module? >>> >>> On Tue, Jul 7, 2015 at 12:18 PM Josh Elser wrote: >>> >>> I committed https://issues.apache.org/jira/browse/ACCUMULO-3929 >>> yesterday. >>> Had a thought today that it might be beneficial to write down how it works somewhere, but I don't know where would be best? Any suggestions? >>
Re: Separate "Performance Tests" execution documentation
To start.. https://github.com/apache/accumulo/blob/master/TESTING.md#performance-tests https://git-wip-us.apache.org/repos/asf?p=accumulo.git;a=blobdiff;f=test/src/main/java/org/apache/accumulo/test/PerformanceTest.java;h=70cc9068a5aa3a517c68cc9c3e0fe7eb105e1466;hp=22fc8897e5fb6f68f2c6fc2260e542af09c71b4f;hb=b411fe3;hpb=dd99cbff20819a02a5c4f7e80e78af473fd8672c LMK on ACCUMULO-3936 if there's anything still unclear (or just clarify it yourself -- doesn't matter either way to me). Josh Elser wrote: I just remembered that Keith made a TESTING.md file https://github.com/apache/accumulo/blob/master/TESTING.md Maybe that would be a logical place? I can add some more Javadoc to the PerformanceTest interface covering how to use it in Java code, but that's probably not a good place to describe how to invoke it. Eric Newton wrote: I would suggest putting it in Javadoc in the PerformanceTest interface. On Tue, Jul 7, 2015 at 12:24 PM, John Vines wrote: README in the top of the testing module? On Tue, Jul 7, 2015 at 12:18 PM Josh Elser wrote: I committed https://issues.apache.org/jira/browse/ACCUMULO-3929 yesterday. Had a thought today that it might be beneficial to write down how it works somewhere, but I don't know where would be best? Any suggestions?
Re: Separate "Performance Tests" execution documentation
I just remembered that Keith made a TESTING.md file https://github.com/apache/accumulo/blob/master/TESTING.md Maybe that would be a logical place? I can add some more Javadoc to the PerformanceTest interface covering how to use it in Java code, but that's probably not a good place to describe how to invoke it. Eric Newton wrote: I would suggest putting it in Javadoc in the PerformanceTest interface. On Tue, Jul 7, 2015 at 12:24 PM, John Vines wrote: README in the top of the testing module? On Tue, Jul 7, 2015 at 12:18 PM Josh Elser wrote: I committed https://issues.apache.org/jira/browse/ACCUMULO-3929 yesterday. Had a thought today that it might be beneficial to write down how it works somewhere, but I don't know where would be best? Any suggestions?
Re: Separate "Performance Tests" execution documentation
I would suggest putting it in Javadoc in the PerformanceTest interface. On Tue, Jul 7, 2015 at 12:24 PM, John Vines wrote: > README in the top of the testing module? > > On Tue, Jul 7, 2015 at 12:18 PM Josh Elser wrote: > > > I committed https://issues.apache.org/jira/browse/ACCUMULO-3929 > yesterday. > > > > Had a thought today that it might be beneficial to write down how it > > works somewhere, but I don't know where would be best? Any suggestions? > > >
Re: Separate "Performance Tests" execution documentation
README in the top of the testing module? On Tue, Jul 7, 2015 at 12:18 PM Josh Elser wrote: > I committed https://issues.apache.org/jira/browse/ACCUMULO-3929 yesterday. > > Had a thought today that it might be beneficial to write down how it > works somewhere, but I don't know where would be best? Any suggestions? >
Separate "Performance Tests" execution documentation
I committed https://issues.apache.org/jira/browse/ACCUMULO-3929 yesterday. Had a thought today that it might be beneficial to write down how it works somewhere, but I don't know where would be best? Any suggestions?
Re: Post 1.5.3 and 1.6.3
I'd like to see the 1.5 EOL happen. On Mon, Jul 6, 2015 at 3:04 PM, Josh Elser wrote: > Thanks to the efforts spearheaded by Christopher and verified by everyone > else, we now have 1.5.3 and 1.6.3 releases! > > To keep the ball rolling, what's next? High level questions that come to > mind... > > * When do we do 1.7.1 and/or 1.8.0? > * What bug-fixes do we have outstanding for 1.7.1? > * What other minor improvements do people want for 1.8.0? > * Where does 2.0.0 stand? Should we make a bigger effort to getting the > new client API stuff Christopher had started into Apache? > > Feel free to brainstorm here and/or on JIRA (tagging relevant issues to > the desired fixVersion) > > - Josh > -- Sean
Re: Post 1.5.3 and 1.6.3
On Mon, Jul 6, 2015 at 4:04 PM, Josh Elser wrote: > Thanks to the efforts spearheaded by Christopher and verified by everyone > else, we now have 1.5.3 and 1.6.3 releases! > > To keep the ball rolling, what's next? High level questions that come to > mind... > > * When do we do 1.7.1 and/or 1.8.0? > * What bug-fixes do we have outstanding for 1.7.1? > * What other minor improvements do people want for 1.8.0? > I am still working on sampling. After that I was thinking of working on some ease of use issues, like optionally sending exceptions from the server side to the client. > * Where does 2.0.0 stand? Should we make a bigger effort to getting the > new client API stuff Christopher had started into Apache? > > Feel free to brainstorm here and/or on JIRA (tagging relevant issues to > the desired fixVersion) > > - Josh >
