Re: Re: Re: Date - bugs fixed in CVS vs 1.4.7
| From: | Helgi Þormar Þorbjörnsson | Date: | Sun, 23 Mar 2008 23:03:36 +0000 |
| Subject: | Re: Re: Re: Date - bugs fixed in CVS vs 1.4.7 | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-49518@lists.php.net to get a copy of this message | ||
Hi
On Sun, Mar 23, 2008 at 10:49 PM, charles woodcock <
charles_woodc@yahoo.co.uk> wrote:
> Hello,
>
> I know someone has kindly made this request on my behalf, but I want to
> release a new version of 'Date' and I need the sufficient privileges to
> access the page:
>
> http://pear.php.net/release-upload.php
>
You are already marked as lead of the package, I assumed you had
pear.devkarma, you do now and you can release :)
>
> Also when I run 'pear package' to create the tgz, I get the message:
> Package Date-1.5.0a1.tgz done
> Tag the released code with `pear cvstag package.xml'
> (or set the CVS tag RELEASE_1_5_0a1 by hand)
>
> I could not find this in the documentation - do I have to do this, and
> what is it anyway? (Actually, I have already run the command and got the
> message:
>
> cvs [server aborted]: "tag" requires write access to the repository
>
> ), but any advice would be appreciated.
run this: pear cvstag package.xml from within your Date dir, it should work
... This is so that all the files in the Date repo get tagged, basically
saying "This is what the files looked like when I did X release", allows for
easy checkouts if you ever feel the urge to get exactly the files you
released 20 years ago ;-)
Plus it makes it a whole lot easier for an outside dev, me for example and
see "Ahh that's what the file looked like 2 releases ago" instead of having
to download the package and looking at the CVS id within each file of that
particular release.
Hope you understand where I was going with this (=
Regards and good luck.
Helgi