Hello,

I couldn't find the tag 2.6 [1], as reported in IO-569 below.

Maybe we skipped some step from "4 Create SCM Tag for the Final Release" in [2] 
? Not too sure if that's really OK just to create manually the tag now, or if 
I've missed something here.

Any thoughts?

Cheers
Bruno


[1] https://git1-us-west.apache.org/repos/asf?p=commons-io.git;a=tags

[2] https://commons.apache.org/releases/release.html




----- Forwarded Message -----
From: Michael Ernst (JIRA) <j...@apache.org>
To: iss...@commons.apache.org 
Sent: Tuesday, 20 February 2018 6:47 PM
Subject: [jira] [Created] (IO-569) Incorrect documentation for cloning 
repository



Michael Ernst created IO-569:

--------------------------------


             Summary: Incorrect documentation for cloning repository

                 Key: IO-569

                 URL: https://issues.apache.org/jira/browse/IO-569

             Project: Commons IO

          Issue Type: Bug

    Affects Versions: 2.6

            Reporter: Michael Ernst



https://commons.apache.org/proper/commons-io/source-repository.html

says:


> Anonymous Access

> 

> The source can be checked out anonymously from Git with this command:

> 

> git clone --branch commons-io-2.6 
> http://git-wip-us.apache.org/repos/asf/commons-io.git


However, when I run that command, I get:


% git clone --branch commons-io-2.6 
http://git-wip-us.apache.org/repos/asf/commons-io.git

Cloning into 'commons-io'...

warning: redirecting to 
https://git1-us-west.apache.org/repos/asf/commons-io.git/

fatal: Remote branch commons-io-2.6 not found in upstream origin


The tags include these:


commons-io-2.5

commons-io-2.5-RC1

commons-io-2.5-RC2

commons-io-2.5-RC3

commons-io-2.5-RC4

commons-io-2.6-RC1

commons-io-2.6-RC2

commons-io-2.6-RC3


but there is no tag for commons-io-2.6.




--

This message was sent by Atlassian JIRA

(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to