Thanks for a wonderful module and a really helpful service on d.o. I hope I am not duplicating #406356, but I don't think I am. Also, since my use of this module is from d.o, and not using it myself, this maybe in current HEAD, and I don't know it.

Anyway, I use CVS to checkout all my modules on projects, but I almost always want a tagged version ("stable" release) of the module. But, as far as I can see on d.o, this module is only providing the branches, which are development releases.

So, I was wondering if you could add the ability to choose a tag and not just a branch. Thank you.

Comments

david strauss’s picture

david strauss
he/him
commented

I could provide the ability to select a tag, but tagged code cannot be altered, so I'd have to remove everything except checking out and creating patches. I'm also worried that allowing selection of tags could confuse users by putting too many options on the list.

How do you think the interface would work for this?

zzolo’s picture

zzolo commented

You make good points. I guess, maybe a good question to ask first is: What is the intended audience(s) here?

I think your (and d.o) intentions are that this module is to help developers (mostly to make patches), hence the note at the top. But for me, my audience is people who use CVS to download and maintain their modules for sites. I see these instructions as another (and more efficient) way to download and update modules, as well as some help for creating patches.

I guess the scope of my request may be out of the goals of this module (and d.o), which may just be to help developers. Or on the flip side, I may be the only person in my audience.

In the case of only supporting developers, I would suggest maybe making the tab name different. To me, "CVS Instructions" imply all CVS operations for this module. Something like "CVS for Developers" seems more appropriate to me. Also, I support #406268: Add the instructions tab on installation profiles to help make it clearer what the tab does before hitting submit.

So, I guess, if you think adding tags is appropriate, I would suggest maybe two forms. One that says "For Developers" with a list of branches. And one that says "To Download" (maybe something better) and a list of tags. Then this would allow for different instructions depending on which is submitted.

Again, thanks for the great module.

--
zzolo

david strauss’s picture

david strauss
he/him
commented

I don't consider your request outside the scope of this module.

zzolo’s picture

zzolo commented

Awesome. What do you think of my suggestion? My time is kind of limited at the moment, so being able to commit a patch any time soon is low, but I would love to try.

--
zzolo

sprugman’s picture

sprugman commented

+1

no_idea_yet’s picture

no_idea_yet commented

+1

Would save a lot of time for those like me, who can't code but use CVS for deploying and maintaining sites.

regards
H