web2py github tags

[Niphlod]

"latest" I get .... "retry" not so much... what's the reasoning behind them ?

[Niphlod]

bump

Also, gi0baro, would it make sense to tag the latest stable pydal release as "latest" and use it as a reference for web2py's submodule ?

Would it short-circuit what happens by mistake updating the module ?

[Giovanni Barillari]

Didn't follow whatever happened on web2py repo, generally the purpose of tags is to stop something in time. So I don't get the point of using a tag for "latest". This is the purpose of a master branch.

[Anthony]

I think "latest" is supposed to mean latest stable release.

[Giovanni Barillari]

Yes but it's pointless. Once you set a tag you can't change it. You should delete it and re-create it in a different point of your repo tree. It won't make any sense. Also because if you delete a tag and I have write permission the next time I will push something, the tag will be recreated in the same point it was. This is git, tag are not supposed to be changed in time.

[Anthony]

Got it. Anyway, if we're using Github releases, we should be able to get the latest via:

https://github.com/web2py/web2py/releases/latest

Anthony

[Niphlod]

ahem. git tags can be moved around pretty easily... they are pointers to commits after all.

I was just trying to have something like "i_know_this_is_it" tag moving from stable to stable release pointing to the last one only

[Giovanni Barillari]

Yes but you actually can't edit them, you just overwrite it with a new one. Anyway, I think a release branch would better suit the need. Look at the weppy repo: whenever I do a release I merge the master on the release one and tag that point with the version. But it's actually the branch that is always the latest release.

[Niphlod]

uhm. and the latest commit on a branch can be tracked as a pointer in the submodule ?

[Dave S]

'tip' or 'head', maybe?

(I speak the other dvcs dialect, so I'm not fluent in git ... I'm just offering a guess) 

/dps

[Giovanni Barillari]

you can track whatever you want in a submodule, because at the end it always track a single commit.

So if the wanted behaviour is the submodule to automatically change the tracked commit, this is not possible. We will always change the track manually.

/Giovanni

[Niphlod]

Okay, bad idea on my side.

[Massimo DiPierro]

I like Simone's idea.

--
-- mail from:GoogleGroups "web2py-developers" mailing list
make speech: web2py-d...@googlegroups.com
unsubscribe: web2py-develop...@googlegroups.com
details : http://groups.google.com/group/web2py-developers
the project: http://code.google.com/p/web2py/
official : http://www.web2py.com/
---
You received this message because you are subscribed to the Google Groups "web2py-developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to web2py-develop...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Giovanni Barillari]

Yes but is not possibile :)

You received this message because you are subscribed to a topic in the Google Groups "web2py-developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/web2py-developers/aeDgqMNVWNw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to web2py-develop...@googlegroups.com.

[Niphlod]

yet another reason to push for pypi package available.............

[Giovanni Barillari]

Touché :)