deleting the 1-0-draft project


#1

Hello all,

For those of you who are following, we are getting pretty close to a release. This means that the sip-communicator-1-0-draft private project is becoming pointless and we are going to move its CVS repository over that of the sip-communicator project.

Collabnet have agreed to do this for free for us (it is normally a paid service), so a big "Thank you!" goes to them!

<snip>
As per your request to move CVS repository from
sip-communicator-1-0-draft to replace the contents of sip-communicator in dev.java.net, we would do this on Tues, 9/12/06 9:30 pm PDT. It should take less than a hour. However, the two projects will be locked during this time. </snip>

We will have to move the issue database ourselves ... Or maybe just stop adding issues in 1-0-draft and wait till they are all closed.

I hope that the move is going to solve common confusion problems that we have had in the past.

Cheers
Emil


#2

Hi Emil,

Thanks for the notice.
As you know I update my repository everyday to build MacOSX packages.
Does it mean that:
- I should "cvs co sip-communicator" instead of sip-communicator-1-0-draft?
- shall I change the nigthly package name (currently
"SIP Communicator-1.0.rc1")?

Regards,
romain

Emil Ivov wrote:

···

Hello all,

For those of you who are following, we are getting pretty close to a release. This means that the sip-communicator-1-0-draft private project is becoming pointless and we are going to move its CVS repository over that of the sip-communicator project.

Collabnet have agreed to do this for free for us (it is normally a paid service), so a big "Thank you!" goes to them!

<snip>
As per your request to move CVS repository from
sip-communicator-1-0-draft to replace the contents of sip-communicator in dev.java.net, we would do this on Tues, 9/12/06 9:30 pm PDT. It should take less than a hour. However, the two projects will be locked during this time. </snip>

We will have to move the issue database ourselves ... Or maybe just stop adding issues in 1-0-draft and wait till they are all closed.

I hope that the move is going to solve common confusion problems that we have had in the past.

Cheers
Emil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

--
Romain KUNTZ
kuntz@sfc.wide.ad.jp

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#3

Hi Romain,

Thanks for the notice.
As you know I update my repository everyday to build MacOSX packages.
Does it mean that:
- I should "cvs co sip-communicator" instead of sip-communicator-1-0-draft?

Yes! I hadn't thought of that. You should indeed update from sip-communicator from now on.

- shall I change the nigthly package name (currently
"SIP Communicator-1.0.rc1")?

I will soon add an ant task that returns the current version of the project and you would be able to use it for the packagke name. Until then you could indeed rename it to SIP Communicator-1.0.alpha1 according to the corresponding release in the roadmap.

http://www.sip-communicator.org/index.php/Development/Roadmap

Cheers
Emil

···

Regards,
romain

Emil Ivov wrote:

Hello all,

For those of you who are following, we are getting pretty close to a release. This means that the sip-communicator-1-0-draft private project is becoming pointless and we are going to move its CVS repository over that of the sip-communicator project.

Collabnet have agreed to do this for free for us (it is normally a paid service), so a big "Thank you!" goes to them!

<snip>
As per your request to move CVS repository from
sip-communicator-1-0-draft to replace the contents of sip-communicator in dev.java.net, we would do this on Tues, 9/12/06 9:30 pm PDT. It should take less than a hour. However, the two projects will be locked during this time. </snip>

We will have to move the issue database ourselves ... Or maybe just stop adding issues in 1-0-draft and wait till they are all closed.

I hope that the move is going to solve common confusion problems that we have had in the past.

Cheers
Emil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#4

Ok, the change seems to have already taken place. Please stop committing to the old repository and use the new one instead.

Cheers
Emil

Emil Ivov wrote:

···

Hello all,

For those of you who are following, we are getting pretty close to a release. This means that the sip-communicator-1-0-draft private project is becoming pointless and we are going to move its CVS repository over that of the sip-communicator project.

Collabnet have agreed to do this for free for us (it is normally a paid service), so a big "Thank you!" goes to them!

<snip>
As per your request to move CVS repository from
sip-communicator-1-0-draft to replace the contents of sip-communicator in dev.java.net, we would do this on Tues, 9/12/06 9:30 pm PDT. It should take less than a hour. However, the two projects will be locked during this time. </snip>

We will have to move the issue database ourselves ... Or maybe just stop adding issues in 1-0-draft and wait till they are all closed.

I hope that the move is going to solve common confusion problems that we have had in the past.

Cheers
Emil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#5

Ok, I have updated the scripts for the nighlty MacOSX packages. From now packages will be named SIP Communicator-1.0.alpha1 and build from sip-communicator repository.

BTW, is there any quota on the download.java.net server? ie shall I regularly delete oldest packages?

romain

Emil Ivov wrote:

···

Hi Romain,

Thanks for the notice.
As you know I update my repository everyday to build MacOSX packages.
Does it mean that:
- I should "cvs co sip-communicator" instead of sip-communicator-1-0-draft?

Yes! I hadn't thought of that. You should indeed update from sip-communicator from now on.

- shall I change the nigthly package name (currently
"SIP Communicator-1.0.rc1")?

I will soon add an ant task that returns the current version of the project and you would be able to use it for the packagke name. Until then you could indeed rename it to SIP Communicator-1.0.alpha1 according to the corresponding release in the roadmap.

http://www.sip-communicator.org/index.php/Development/Roadmap

Cheers
Emil

Regards,
romain

Emil Ivov wrote:

Hello all,

For those of you who are following, we are getting pretty close to a release. This means that the sip-communicator-1-0-draft private project is becoming pointless and we are going to move its CVS repository over that of the sip-communicator project.

Collabnet have agreed to do this for free for us (it is normally a paid service), so a big "Thank you!" goes to them!

<snip>
As per your request to move CVS repository from
sip-communicator-1-0-draft to replace the contents of sip-communicator in dev.java.net, we would do this on Tues, 9/12/06 9:30 pm PDT. It should take less than a hour. However, the two projects will be locked during this time. </snip>

We will have to move the issue database ourselves ... Or maybe just stop adding issues in 1-0-draft and wait till they are all closed.

I hope that the move is going to solve common confusion problems that we have had in the past.

Cheers
Emil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

--
Romain KUNTZ
kuntz@sfc.wide.ad.jp

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#6

Hi,

I'm using JBuilder and on the config for the CVS I cannot change the module name. Is there any other way to change
without making new project ?

damencho

···

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#7

Ok, I have updated the scripts for the nighlty MacOSX packages. From now packages will be named SIP Communicator-1.0.alpha1 and build from sip-communicator repository.

great! that was quick

BTW, is there any quota on the download.java.net server? ie shall I regularly delete oldest packages?

Actually, I don't really know. I don't think there is one but we could still behave responsibly. Regularly deleting old packages is a good idea. I think that 10 days of nightly builds is enough.

Are you going to delete them manually. If this is the case, I guess you could bring them down to 10 every month or so. What do you think?

Emil

···

romain

Emil Ivov wrote:

Hi Romain,

Thanks for the notice.
As you know I update my repository everyday to build MacOSX packages.
Does it mean that:
- I should "cvs co sip-communicator" instead of sip-communicator-1-0-draft?

Yes! I hadn't thought of that. You should indeed update from sip-communicator from now on.

- shall I change the nigthly package name (currently
"SIP Communicator-1.0.rc1")?

I will soon add an ant task that returns the current version of the project and you would be able to use it for the packagke name. Until then you could indeed rename it to SIP Communicator-1.0.alpha1 according to the corresponding release in the roadmap.

http://www.sip-communicator.org/index.php/Development/Roadmap

Cheers
Emil

Regards,
romain

Emil Ivov wrote:

Hello all,

For those of you who are following, we are getting pretty close to a release. This means that the sip-communicator-1-0-draft private project is becoming pointless and we are going to move its CVS repository over that of the sip-communicator project.

Collabnet have agreed to do this for free for us (it is normally a paid service), so a big "Thank you!" goes to them!

<snip>
As per your request to move CVS repository from
sip-communicator-1-0-draft to replace the contents of sip-communicator in dev.java.net, we would do this on Tues, 9/12/06 9:30 pm PDT. It should take less than a hour. However, the two projects will be locked during this time. </snip>

We will have to move the issue database ourselves ... Or maybe just stop adding issues in 1-0-draft and wait till they are all closed.

I hope that the move is going to solve common confusion problems that we have had in the past.

Cheers
Emil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#8

Hi,

I thought I had the answer to this one but now that I think it may not be that simple.

I thought one could manually commit modifications by specifying a custom root via the command line:

cvs -d :pserver:damencho@cvs.dev.java.net:/cvs commit <params>

Which is not entirely false but we haven't changed the cvs root here ... only the project name.

I wonder whether there's a plain way of doing this ... if not, we could always try to replace all occurrences of sip-communicator-1-0-draft by sip-communicator in the CVS directories.

Any ideas?

Emil

Damian Minkov wrote:

···

Hi,

I'm using JBuilder and on the config for the CVS I cannot change the module name. Is there any other way to change
without making new project ?

damencho

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#9

Hi Emil,

Emil Ivov wrote:

Are you going to delete them manually. If this is the case, I guess you could bring them down to 10 every month or so. What do you think?

I have added a task in the crontab on download.java.net, that deletes all directories of the previous month on the 10th of each month. Does it sounds ok?

···

--
Romain KUNTZ
kuntz@sfc.wide.ad.jp

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#10

That is what you need to do -- replace the old module name with the new
one in all of the CVS/Repository files. cvs does not provide a command
to do this in one step. In the past I've combined bash, find and vim to
accomplish this. Something like this (but I haven't tested it this
time):
    for F in `find . -path \*/CVS/Repository` ; do vim -c
':s,-1-0-draft/,/,' -c ':wq' ; done

One project I worked with had a script they used for updating working
copies when the repository changed. Other cvs-related tools (maybe
eclipse) provide this functionality. svn provides a command to make
this easy without using external tools.

HTH,
-D

···

On Wed, 2006-09-13 at 15:32 +0200, Emil Ivov wrote:

Hi,

I thought I had the answer to this one but now that I think it may not
be that simple.

I thought one could manually commit modifications by specifying a custom
root via the command line:

cvs -d :pserver:damencho@cvs.dev.java.net:/cvs commit <params>

Which is not entirely false but we haven't changed the cvs root here ...
only the project name.

I wonder whether there's a plain way of doing this ... if not, we could
always try to replace all occurrences of sip-communicator-1-0-draft by
sip-communicator in the CVS directories.

Any ideas?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#11

Great tip Derrick!

I didn't know one could use vim for text processing in shell scripts. This is really great!

I've used your command on my sandbox and it worked.

I needed to modify it slightly though

for F in `find . -path \*/CVS/Repository` ; do vim $F -c ':s/-1-0-draft//' -c ':wq' ; done

Added the $F and changed vim's substitute string (the latter may turn out to be specific for my vim version)

The first cvs update after I had run the script took longer than usual (wonder why) but completed without an error.

Thanks again for the script!

Cheers
Emil

Derrick Hudson wrote:

···

On Wed, 2006-09-13 at 15:32 +0200, Emil Ivov wrote:

Hi,

I thought I had the answer to this one but now that I think it may not be that simple.

I thought one could manually commit modifications by specifying a custom root via the command line:

cvs -d :pserver:damencho@cvs.dev.java.net:/cvs commit <params>

Which is not entirely false but we haven't changed the cvs root here ... only the project name.

I wonder whether there's a plain way of doing this ... if not, we could always try to replace all occurrences of sip-communicator-1-0-draft by sip-communicator in the CVS directories.

Any ideas?

That is what you need to do -- replace the old module name with the new
one in all of the CVS/Repository files. cvs does not provide a command
to do this in one step. In the past I've combined bash, find and vim to
accomplish this. Something like this (but I haven't tested it this
time):
    for F in `find . -path \*/CVS/Repository` ; do vim -c
':s,-1-0-draft/,/,' -c ':wq' ; done

One project I worked with had a script they used for updating working
copies when the repository changed. Other cvs-related tools (maybe
eclipse) provide this functionality. svn provides a command to make
this easy without using external tools.

HTH,
-D

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#12

Romain KUNTZ wrote:

I have added a task in the crontab on download.java.net, that deletes all directories of the previous month on the 10th of each month. Does it sounds ok?

Also, the directory listing is automatically updated.
Take a look at the ~/sip-communicator/nightly/macosx/rm-dir.sh script

···

--
Romain KUNTZ
kuntz@sfc.wide.ad.jp

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#13

Hi Romain

Romain KUNTZ wrote:

I have added a task in the crontab on download.java.net, that deletes all directories of the previous month on the 10th of each month. Does it sounds ok?

Hm. What happens if we haven't had modifications, and therefore no nightly either, until the 10th of the new month?

Would it be possible to remove all except the one that "latest" link points to?

Emil


#14

Great tip Derrick!

I didn't know one could use vim for text processing in shell scripts.
This is really great!

Yeah. The '-c' argument means run this command. Including '-c :wq' has
it save and quit, which is the key to using it that way.

I've used your command on my sandbox and it worked.

I needed to modify it slightly though

> for F in `find . -path \*/CVS/Repository` ; do vim $F -c ':s/-1-0-draft//' -c ':wq' ; done

Added the $F

Oops. That's what I get for coding in an email instead of at the
shell :).

and changed vim's substitute string (the latter may turn
out to be specific for my vim version)

That doesn't (shouldn't) make a difference. vim, and sed and some other
regex tools, allow any single character as the delimiter. I chose to
use a comma because it's easy to type and I chose to keep the / that
follows -draft in the pattern as a sort of anchor (just in case
-1-0-draft occurred anywhere else in the text) and also had / in the
substitution pattern to not lose the /. Your pattern works just as well
since the input data didn't actually need anything else to ensure
nothing undesired was matched.

The first cvs update after I had run the script took longer than usual
(wonder why) but completed without an error.

I don't know. Maybe some coincidence with network or disk loads or
cache misses or something.

Thanks again for the script!

You're welcome.

-D

···

On Wed, 2006-09-13 at 18:20 +0200, Emil Ivov wrote:

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#15

Hi Emil,

Emil Ivov wrote:

Hm. What happens if we haven't had modifications, and therefore no nightly either, until the 10th of the new month?

Actually, I build a package every night event though no modifications have been done (actually I do not check if modifications have been done or not). Would you prefer to build packages only upon modifications?

···

--
Romain KUNTZ
kuntz@sfc.wide.ad.jp

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#16

Romain KUNTZ wrote:

Hi Emil,

Emil Ivov wrote:

Hm. What happens if we haven't had modifications, and therefore no nightly either, until the 10th of the new month?

Actually, I build a package every night event though no modifications have been done (actually I do not check if modifications have been done or not). Would you prefer to build packages only upon modifications?

No, it's fine, I don't mind.

Emil