#3286 Tags sorted in random way. Mercurial code browser [22807]

unreleased
open
nobody
SCM
nobody
2015-02-09
2011-11-18
Chris Tsai
No

https://sourceforge.net/apps/trac/sourceforge/ticket/22807

Visit:

https://sourceforge.net/p/jdone/code/?branch=ref%2Fdefault

and you see:

Tags

t0.2 66
t0.3 78
t0.1 23
tip 80

t0.3 below t0.2!

I expect that tats was sorted reverse chronological (most recent on top).

If that's not it, can you explain the sorting method?

Discussion

  • Anonymous - 2011-11-18

    Originally by: gavenkoa

    When I release software I tag release with name like v2.3.4 or t3.4 (prefix t used to distinct from named branches in HG).

    I expect that last created tags was listened firstly as a few people care about old releases. All usually need new code.

    In my example tag 0.2 is 66 rev and must follow tag 0.3 which in 78 rev. But 0.3 after 0.2! Also 'tip' is special tag for HG and it mark last changeset in repo. It was shown last but definitely must stay first...

     
  • Dave Brondsema

    Dave Brondsema - 2012-06-13
    • milestone: limbo --> forge-backlog
     
  • Anonymous - 2012-06-21

    Originally by: gavenkoa

    On 2012-06-13, Dave Brondsema wrote:

    [tickets:3286] Tags sorted in random way. Mercurial code browser [22807]

    Status: open
    Labels: support
    Created: Fri Nov 18, 2011 02:56 PM UTC by Christopher Tsai
    Last Updated: Fri Nov 18, 2011 11:09 PM UTC
    Owner: nobody

    https://sourceforge.net/apps/trac/sourceforge/ticket/22807

    Visit:

    https://sourceforge.net/p/jdone/code/?branch=ref%2Fdefault

    and you see:

    Tags

    t0.2 66
    t0.3 78
    t0.1 23
    tip 80

    t0.3 below t0.2!

    I expect that tats was sorted reverse chronological (most recent on top).

    If that's not it, can you explain the sorting method?

    Hi!

    I explain my vision for tag sorting at

    http://sourceforge.net/p/allura/tickets/3286/

    From there:

    When I release software I tag release with name like v2.3.4 or t3.4 (prefix
    t used to distinct from named branches in HG).

    I expect that last created tags was listened firstly as a few people care
    about old releases. All usually need new code.

    In my example tag 0.2 is 66 rev and must follow tag 0.3 which in 78 rev. But
    0.3 after 0.2! Also 'tip' is special tag for HG and it mark last changeset
    in repo. It was shown last but definitely must stay first...

    Currently situation for tag list in:

    http://sourceforge.net/p/jdone/code/?branch=ref%2Fdefault

    look as:

    t0.2 65
    t0.3 77
    t0.1 22
    tip 155
    t0.4 121
    t0.5 154

    Sort order is silly. I expect to have:

    tip 155
    t0.5 154
    t0.4 121
    t0.3 77
    t0.2 65
    t0.1 22

    --
    Best regards!

     
  • Chris Tsai - 2012-09-26
    • labels: support --> support, p3
     
  • Dave Brondsema

    Dave Brondsema - 2014-06-30
    • labels: support, p3 --> support, p3, bitesize
     

Log in to post a comment.