accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1498) Create document to outline step to Git transition
Date Thu, 06 Jun 2013 21:44:20 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13677548#comment-13677548
] 

Christopher Tubbs commented on ACCUMULO-1498:
---------------------------------------------

{quote}
Actions:
1. Need to remember to request this
{quote}

We could rename the branch ourselves if necessary, but probably they'd need to do it for us
so it's the default branch when cloning.

{quote}
4. Probably/Maybe? I'm not sure how robust git+svn clone is here. Verification/validation
before the transition is complete would be necessary.
{quote}

Right now, I'm pretty sure the branches *don't* merge cleanly, so it would be very annoying
if this made git branches not merge cleanly. If fixing it in SVN first will make git-svn and
git happy later, we should do that. I'd really love to close the 1.3 branch prior to switching...
it's one less branch we'd have to deal with. I'd also like to get this transition done *prior*
to releasing 1.6.0, so we don't add another branch in the chain to deal with.

{quote}
5. Not sure I follow this one. SVN branches will appear as git branches, and SVN tags as git
tags. Verification/validation again.
{quote}

Right, but these are the long-running old versions branches we've discussed. This is related
to number 4. The main point being that eventually, all the last tags in each series should
merge forward cleanly. What we don't want to do is tag them without making them merge cleanly
first... that would be *VERY* frustrating when doing bugfixes in older versions.

{quote}
6. Should pre-date 5
{quote}

Number 5 would create some more... unless you're including branch cleanup as part of the tagging
process, then we're thinking similarly.
                
> Create document to outline step to Git transition
> -------------------------------------------------
>
>                 Key: ACCUMULO-1498
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1498
>             Project: Accumulo
>          Issue Type: Task
>          Components: docs
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>         Attachments: ctubbsii-git-proposed-actions.v1.txt, ctubbsii-git-suggestions.v1.txt
>
>
> We need to outline both how we plan to use Git (for those who are not familiar with it)
and the steps necessary to get the infrastructure in place.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message