Re: [Lucene.Net] Is a Lucene.Net Line-by-Line Jave port needed?
My thinking is just a separate ticket for each one. This makes the work
easier to manage and gives a better sense about how much work is left as
well as makes it easier to prioritize independent issues. We could link all
the sub-issues to a single task / feature / whatever (that is, if JIRA has
that capability).
-r
On Fri, Jul 1, 2011 at 12:48 PM, Michael Herndon
mhern...@wickedsoftware.net wrote:
I think whatever makes sense to do.
possibly create one jira for now with a running list that can be modified
and possibly as people pull from that list, cross things off or create a
separate ticket that links back to to the main one.
On Fri, Jul 1, 2011 at 3:35 PM, Rory Plaire codekai...@gmail.com wrote:
@Michael -
Should that list be in JIRA? It would be easier to manage, I think...
If yes, I'll happily do it.
-r
On Fri, Jul 1, 2011 at 8:04 AM, Michael Herndon
mhern...@wickedsoftware.net
wrote:
* need to document what the build script does. whut grammerz?
On Fri, Jul 1, 2011 at 10:52 AM, Michael Herndon
mhern...@wickedsoftware.net wrote:
@Rory, @All,
The only tickets I currently have for those is LUCENE-419, LUCENE-418
418, I should be able to push into the 2.9.4g branch tonight.419
is
a
long term goal and not as important as getting the tests fixed, of
have
the
tests broken down into what is actually a unit test, functional test,
perf
or long running test. I can get into more why it needs to be done.
I'll also need to make document the what build script currently does
on
the
wiki and make a few notes about testing, like using the
RAMDirectory,
etc.
Things that need to get done or even be discussed.
* There needs to be a running list of things to do/not to do with
testing.
I don't know if this goes in a jira or do we keep a running list on
the
wiki
or site for people to pick up and help with.
* Tests need to run on mono and not Fail (there is a good deal of
failing
tests on mono, mostly due to the temp directory have the C:\ in the
path).
* Assert.ThrowExceptionType() needs to be used instead of
Try/Catch
Assert.Fail. **
* File Path combines to the temp directory need helper methods,
* e,g, having this in a hundred places is bad new
System.IO.FileInfo(System.IO.Path.Combine(Support.AppSettings.Get(tempDir,
), testIndex));
* We should still be testing deprecated methods, but we need to use
#pragma
warning disable/enable 0618 for testing those. otherwise compiler
warnings
are too numerous to be anywhere near helpful.
* We should only be using deprecated methods in places where they
are
being explicitly tested, other tests that need that functionality in
order
to validate those tests should be re factored to use methods that are
not
deprecated.
* Identify code that could be abstracted into test utility classes.
* Infrastructure Validation tests need to be made, anything that
seems
like infrastructure. e.g. does the temp directory exist, does the
folders
that the tests use inside the temp directory exist, can we read/write
to
those folders. (if a ton of tests fail due to the file system, we
should
be
able to point out that it was due to permissions or missing folders,
files,
etc).
* Identify what classes need an interface, abstract class or
inherited
in
order to create testing mocks. (once those classes are created, they
should
be documented in the wiki).
** Asset.Throws needs to replace stuff like the following. We should
also
be checking the messages for exceptions and make sure they make sense
and
can help users fix isses if the exceptions are aimed at the library
users.
try
{
d = DateTools.StringToDate(97); // no date
Assert.Fail();
}
catch (System.FormatException e)
{
/* expected exception */
}
On Thu, Jun 30, 2011 at 11:48 PM, Rory Plaire codekai...@gmail.com
wrote:
So, veering towards action - are there concrete tasks written up
anywhere
for the unit tests? If a poor schlep like me wanted to dig in and
start
to
improve them, where would I get the understanding of what is good
and
what
needs help?
-r
On Thu, Jun 30, 2011 at 3:29 PM, Digy digyd...@gmail.com wrote:
I can not say I like this approach, but till we find an automated
way(with
good results), it seems to be the only way we can use.
DIGY
-Original Message-
From: Troy Howard [mailto:thowar...@gmail.com]
Sent: Friday, July 01, 2011 12:43 AM
To: lucene-net-dev@lucene.apache.org
Subject: Re: [Lucene.Net] Is a Lucene.Net Line-by-Line Jave port
needed?
Scott -
The idea of the automated port is still worth doing. Perhaps it
makes
[Lucene.Net] [jira] [Commented] (LUCENENET-404) Improve brand logo design
[ https://issues.apache.org/jira/browse/LUCENENET-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13058761#comment-13058761 ] Troy Howard commented on LUCENENET-404: --- Just a quick update. The artist is making some final edits before we commit. Will post them soon. I'll attach examples. Improve brand logo design - Key: LUCENENET-404 URL: https://issues.apache.org/jira/browse/LUCENENET-404 Project: Lucene.Net Issue Type: Sub-task Components: Project Infrastructure Reporter: Troy Howard Assignee: Troy Howard Priority: Minor Labels: branding, logo The existing Lucene.Net logo leaves a lot to be desired. We'd like a new logo that is modern and well designed. To implement this, Troy is coordinating with StackOverflow/StackExchange to manage a logo design contest, the results of which will be our new logo design. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [Lucene.Net] Is a Lucene.Net Line-by-Line Jave port needed?
@Rory,
Jira in the past had the ability to create sub tasks or convert a current
task to a sub task. I'm guessing that apache's jira should be able to do
that.
@All,
I've add a Paths Class under the Lucene.Net.Tests Util folder (feel free to
rename, refactor as long as the tests still work) to help with working with
paths in general. This should help with forming paths relative to the temp
directory or the project root.
NUnit's Shadow Copy tends to throw people off when trying to get the path of
the current assembly being tested to build up a relative path, the Path
class should help with that.
- Michael
On Fri, Jul 1, 2011 at 4:09 PM, Rory Plaire codekai...@gmail.com wrote:
My thinking is just a separate ticket for each one. This makes the work
easier to manage and gives a better sense about how much work is left as
well as makes it easier to prioritize independent issues. We could link all
the sub-issues to a single task / feature / whatever (that is, if JIRA has
that capability).
-r
On Fri, Jul 1, 2011 at 12:48 PM, Michael Herndon
mhern...@wickedsoftware.net wrote:
I think whatever makes sense to do.
possibly create one jira for now with a running list that can be modified
and possibly as people pull from that list, cross things off or create a
separate ticket that links back to to the main one.
On Fri, Jul 1, 2011 at 3:35 PM, Rory Plaire codekai...@gmail.com
wrote:
@Michael -
Should that list be in JIRA? It would be easier to manage, I think...
If yes, I'll happily do it.
-r
On Fri, Jul 1, 2011 at 8:04 AM, Michael Herndon
mhern...@wickedsoftware.net
wrote:
* need to document what the build script does. whut grammerz?
On Fri, Jul 1, 2011 at 10:52 AM, Michael Herndon
mhern...@wickedsoftware.net wrote:
@Rory, @All,
The only tickets I currently have for those is LUCENE-419,
LUCENE-418
418, I should be able to push into the 2.9.4g branch tonight.
419
is
a
long term goal and not as important as getting the tests fixed, of
have
the
tests broken down into what is actually a unit test, functional
test,
perf
or long running test. I can get into more why it needs to be done.
I'll also need to make document the what build script currently
does
on
the
wiki and make a few notes about testing, like using the
RAMDirectory,
etc.
Things that need to get done or even be discussed.
* There needs to be a running list of things to do/not to do with
testing.
I don't know if this goes in a jira or do we keep a running list on
the
wiki
or site for people to pick up and help with.
* Tests need to run on mono and not Fail (there is a good deal of
failing
tests on mono, mostly due to the temp directory have the C:\ in the
path).
* Assert.ThrowExceptionType() needs to be used instead of
Try/Catch
Assert.Fail. **
* File Path combines to the temp directory need helper methods,
* e,g, having this in a hundred places is bad new
System.IO.FileInfo(System.IO.Path.Combine(Support.AppSettings.Get(tempDir,
), testIndex));
* We should still be testing deprecated methods, but we need to
use
#pragma
warning disable/enable 0618 for testing those. otherwise compiler
warnings
are too numerous to be anywhere near helpful.
* We should only be using deprecated methods in places where they
are
being explicitly tested, other tests that need that functionality
in
order
to validate those tests should be re factored to use methods that
are
not
deprecated.
* Identify code that could be abstracted into test utility
classes.
* Infrastructure Validation tests need to be made, anything that
seems
like infrastructure. e.g. does the temp directory exist, does the
folders
that the tests use inside the temp directory exist, can we
read/write
to
those folders. (if a ton of tests fail due to the file system, we
should
be
able to point out that it was due to permissions or missing
folders,
files,
etc).
* Identify what classes need an interface, abstract class or
inherited
in
order to create testing mocks. (once those classes are created,
they
should
be documented in the wiki).
** Asset.Throws needs to replace stuff like the following. We
should
also
be checking the messages for exceptions and make sure they make
sense
and
can help users fix isses if the exceptions are aimed at the library
users.
try
{
d = DateTools.StringToDate(97); // no date
Assert.Fail();
}
catch (System.FormatException e)
{
/* expected exception */
}
On Thu, Jun 30, 2011 at 11:48 PM, Rory Plaire
codekai...@gmail.com
wrote:
So, veering towards
[Lucene.Net] [jira] [Work started] (LUCENENET-404) Improve brand logo design
[ https://issues.apache.org/jira/browse/LUCENENET-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on LUCENENET-404 started by Troy Howard. Improve brand logo design - Key: LUCENENET-404 URL: https://issues.apache.org/jira/browse/LUCENENET-404 Project: Lucene.Net Issue Type: Sub-task Components: Project Infrastructure Reporter: Troy Howard Assignee: Troy Howard Priority: Minor Labels: branding, logo Attachments: lucene-alternates.jpg, lucene-medium.png, lucene-net-logo-display.jpg The existing Lucene.Net logo leaves a lot to be desired. We'd like a new logo that is modern and well designed. To implement this, Troy is coordinating with StackOverflow/StackExchange to manage a logo design contest, the results of which will be our new logo design. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
