[
https://issues.apache.org/jira/browse/UIMA-6115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16911697#comment-16911697
]
Marshall Schor edited comment on UIMA-6115 at 8/20/19 8:00 PM:
---------------------------------------------------------------
Current plan:
# merged project will be "uimaj" (the current place uimaj v2 is)
# the existing uimaj trunk (holding v2) will be moved to branches/2.x
# its trunk will become the current uimaj-v3 trunk.
# the uimaj-v3 tags will be copied into the uimaj/tags
Current users who have checked out from SVN will need to update their
checkouts, and probably should refrain from doing anything until the writable
git support is turned on.
was (Author: schor):
Current plan:
# merged project will be "uimaj" (the current place uimaj v2 is)
# it will have a new top-level node named master being the uimaj-v3 trunk.
# the existing uimaj trunk (holding v2) will be moved to branches/2.x
# the uimaj-v3 tags will be copied into the uimaj/tags
Current users who have checked out from SVN will need to update their
checkouts, and probably should refrain from doing anything until the writable
git support is turned on.
> uv3 move uimaj-v3 as a branch under uimaj
> -----------------------------------------
>
> Key: UIMA-6115
> URL: https://issues.apache.org/jira/browse/UIMA-6115
> Project: UIMA
> Issue Type: Task
> Components: Core Java Framework
> Affects Versions: 3.1.0SDK
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Priority: Minor
> Fix For: 3.1.1SDK
>
>
> As part of this, merge the tags as needed. This will allow one repo for
> uimaj in github which has been requested by several people.
> Since this branch will serve as the "trunk" or master for the v3 version,
> consider a branch name that denotes that.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
