| Summary | Add current date to CVS snapshots' version numbers |
| Queue | Horde.org Servers |
| Type | Enhancement |
| State | Rejected |
| Priority | 1. Low |
| Owners | |
| Requester | webmaster (at) dasourcerer (dot) net |
| Created | 01/17/2007 (6767 days ago) |
| Due | |
| Updated | 01/18/2007 (6766 days ago) |
| Assigned | |
| Resolved | 01/18/2007 (6766 days ago) |
| Milestone | |
| Patch | No |
State ⇒ Rejected
to have the same version tags for regular CVS checkouts too, to make
any sense.
State ⇒ Feedback
somehow, but on the other, they are tagged in their filename, and
modifying the contents of the tarball would mean they no longer
reflected the actual CVS code as it was when the snapshot was made. In
a very trivial way, of course, but still.
Also, the snapshots are a convenience for people who can't or don't
want to use CVS, not really an officially supported release, so from
our perspective letting people know exactly what snapshot they have
doesn't do us much good - we want them to have the latest one.
Other opinions?
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ Add current date to CVS snapshots' version numbers
Queue ⇒ Horde.org Servers
State ⇒ New
whups v1.0-cvs would turn into whups v1.0-cvs20070117. I founf out
this can be done with one line of shellcode:
sed -i -e s/cvs/cvs`date +%Y%m%d`/ version.php
The main reason is: If I've got experimental software installed, it's
much easier to keep track on what's been installed when. Currently, I
just keep the downloaded .tar.gz which isn't as handy.