Admin Panel shows Installed "v1.3.0.beta2 +2"


#1

Current version: 4714a56
Remote version: a26853c

Haven’t seen this +2 thing before, seems strange to me.


(cpradio) #2

It is new. It shows up when you visit the /upgrade page and perform an upgrade to get the latest commits when an official beta hasn’t been released yet.


(Michael Downey) #3

It’s programmer-speak. They use it in their Git version tracking software to see how far ahead or behind they are against a milestone. Not sure that it’s useful for mere mortals without some context, though. :slight_smile:


#4

Oh I see. Haven’t read about this before :slight_smile: Thanks!


(cpradio) #5

See


#6

But isn’t it broken then? It shows +2 in the Panel and 22 new commits at /admin/upgrade.

cc @riking


(cpradio) #7

No. You are 22 commits behind latest (which isn’t the latest beta release, but rather latest commit into beta branch). There hasn’t been another beta release yet.

So you are on the latest release, but you are not using the latest code checked in to beta.


(Kane York) #8

Well, it actually says “26 new commits”.
What that means is that if you upgraded, you would move to v1.3.0.beta2 +28.

We can use the plus version for talking about when a feature is released.

edit: Just noticed that there’s an extra ‘v’ on the front…


#9

Ooohhh now I’m getting it! :blush:
What a confusion, heh.


(Sam Saffron) #10

Maybe we should just cheat here and write

v1.3.0.28 (beta2)

It feels more like a version number and will limit confusion.


(Kane York) #11

Problem with that is that #4 will reset when the beta increments. (It counts back to the most recent tag)


(Jeff Atwood) #12

Maybe it should be

v1.3.0 (beta 2.28)

then?


(Sam Saffron) #13

Not following, we increment minor after every beta


(Kane York) #14

No… in that layout, it would go like this:

v1.3.0.28 (beta2)
v1.3.0.29 (beta2)
v1.3.0.1 (beta3)
v1.3.0.2 (beta3)

Versus

v1.3.0.beta2 +28
v1.3.0.beta2 +29
v1.3.0.beta3 +1
v1.3.0.beta3 +2


(Jens Maier) #15

This might not be semantically correct, but how about this:

1.3.0.beta2-r28
1.3.0.beta2-r29
1.3.0.beta3
1.3.0.beta3-r1
etc.


(Kane York) #16

Sure, that could work. It keeps the order correct.