[
https://issues.apache.org/jira/browse/OOZIE-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068030#comment-13068030
]
Chris Douglas commented on OOZIE-1:
-----------------------------------
(not sure why bq. isn't quoting; haven't found any related admin settings...)
Yes, re-releasing any former version would require going through the process
for each artifact, which is likely not worthwhile. However, creating release
branches (for bug fixes, etc.) might be useful and found/fixed versions could
be set in JIRA and correlated with a branch in SVN. If it's not much work on
the import, it's helpful for bookkeeping. If it turns into a hassle, defining
trunk is sufficient.
> Initial import of Oozie codebase
> --------------------------------
>
> Key: OOZIE-1
> URL: https://issues.apache.org/jira/browse/OOZIE-1
> Project: Apache Oozie (Incubating)
> Issue Type: Task
> Reporter: Chris Douglas
> Assignee: Mohammad Kamrul Islam
>
> Marker for initial import from https://github.com/yahoo/oozie
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
