lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doron Cohen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LUCENE-1157) Formatable changes log (CHANGES.txt is easy to edit but not so friendly to read by Lucene users)
Date Wed, 06 Feb 2008 18:35:08 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12566257#action_12566257
] 

Doron Cohen commented on LUCENE-1157:
-------------------------------------

Nice spying work Steven :)

I am not familiar with Hudson configuration, but job/Lucene-trunk/ws/  sounds like a temporary
work space, that might be erased during builds[?].

"artifacts" that are saved at the end of a successful build seem stable/proper. 
We need the entire changes directory - actually the 3 files in it - is "changes" an ok name
for an "artifact" directory? 

> Formatable changes log  (CHANGES.txt is easy to edit but not so friendly to read by Lucene
users)
> -------------------------------------------------------------------------------------------------
>
>                 Key: LUCENE-1157
>                 URL: https://issues.apache.org/jira/browse/LUCENE-1157
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Website
>            Reporter: Doron Cohen
>            Assignee: Doron Cohen
>             Fix For: 2.4
>
>         Attachments: lucene-1157-take2.patch, lucene-1157-take3.patch, lucene-1157.patch
>
>
> Background in http://www.nabble.com/formatable-changes-log-tt15078749.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message