Re: moving code from sandbox to proper - best practice?
Hi!
I wanted to start the move of VFS from sandbox to proper and wasnt aware
that these questions are not solved yet.
The main question that needs resolving is:
* should the code be MOVED from sandbox to proper, or COPIED?
I would like to tag the current sandbox to /tags/sandbox ...
I think my preference would be
* move the existing code to {proj}/tags/sandbox
... and then MOVE it to proper.
* create a new sandbox/{proj} directory, containing just a README
that points to the new project.
I guess the last statement was not to leave any clutter.
I do not have any strong preferences here, but I think this README is
not needet as a active developer knows whats going on.
Should I copy the page
http://wiki.apache.org/jakarta-commons/MovingFromSandboxToProper to
MovingFromSandboxToProperSVN and record all my steps there?
---
Mario
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: moving code from sandbox to proper - best practice?
I disagree, README is just clutter and should be removed.
We send out announcements on the mailing list and if people miss that
they can look at the website.
The complete list of components if on the commons homepage so with one
click you have a full overview.
-- Dirk
Rory Winston wrote:
Good question. We did look at doing a sandbox cleanup when it was migrated from
CVS to SVN. I remember doing a list of dead projects that were still in
sandbox. However, I agree that having a sandbox/{project} dir with at the very
least a README pointing to the new location (for promoted components) would be
useful.
[EMAIL PROTECTED] wrote:
Hi,
The moving from sandbox to proper wiki page needs updating, as it is
all CVS based.
http://wiki.apache.org/jakarta-commons/MovingFromSandboxToProper
The main question that needs resolving is:
* should the code be MOVED from sandbox to proper, or COPIED?
Moving the code means that links to the old location break. But copying
the code means that links to the old stuff don't give any indication
that the main development is now happening elsewhere.
What do people think the best practice is for sandbox-proper promotion?
I think my preference would be
* move the existing code to {proj}/tags/sandbox
* copy to {proj}/trunk
* create a new sandbox/{proj} directory, containing just a README
that points to the new project.
That way, all the sandbox code vanishes from its old location, avoiding
any confusion. But users of the sandbox stuff at least get a hint where
the new stuff is.
The main disadvantage is clutter left in the sandbox directory.
Thoughts?
Regards,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: moving code from sandbox to proper - best practice?
I think I agree with this. I believe it is better to remove the entire
sandbox directory, so that people notice it has moved (the website says
where) and can change the SVN repository in use (that can be done; can't it?).
At 2005-05-13 10:10, you wrote:
I disagree, README is just clutter and should be removed.
We send out announcements on the mailing list and if people miss that they
can look at the website.
The complete list of components if on the commons homepage so with one
click you have a full overview.
-- Dirk
Rory Winston wrote:
Good question. We did look at doing a sandbox cleanup when it was
migrated from CVS to SVN. I remember doing a list of dead projects that
were still in sandbox. However, I agree that having a sandbox/{project}
dir with at the very least a README pointing to the new location (for
promoted components) would be useful.
[EMAIL PROTECTED] wrote:
Hi,
The moving from sandbox to proper wiki page needs updating, as it is
all CVS based.
http://wiki.apache.org/jakarta-commons/MovingFromSandboxToProper
The main question that needs resolving is:
* should the code be MOVED from sandbox to proper, or COPIED?
Moving the code means that links to the old location break. But copying
the code means that links to the old stuff don't give any indication
that the main development is now happening elsewhere.
What do people think the best practice is for sandbox-proper promotion?
I think my preference would be
* move the existing code to {proj}/tags/sandbox
* copy to {proj}/trunk
* create a new sandbox/{proj} directory, containing just a README
that points to the new project.
That way, all the sandbox code vanishes from its old location, avoiding
any confusion. But users of the sandbox stuff at least get a hint where
the new stuff is.
The main disadvantage is clutter left in the sandbox directory.
Thoughts?
Regards,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
moving code from sandbox to proper - best practice?
Hi,
The moving from sandbox to proper wiki page needs updating, as it is
all CVS based.
http://wiki.apache.org/jakarta-commons/MovingFromSandboxToProper
The main question that needs resolving is:
* should the code be MOVED from sandbox to proper, or COPIED?
Moving the code means that links to the old location break. But copying
the code means that links to the old stuff don't give any indication
that the main development is now happening elsewhere.
What do people think the best practice is for sandbox-proper promotion?
I think my preference would be
* move the existing code to {proj}/tags/sandbox
* copy to {proj}/trunk
* create a new sandbox/{proj} directory, containing just a README
that points to the new project.
That way, all the sandbox code vanishes from its old location, avoiding
any confusion. But users of the sandbox stuff at least get a hint where
the new stuff is.
The main disadvantage is clutter left in the sandbox directory.
Thoughts?
Regards,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: moving code from sandbox to proper - best practice?
Good question. We did look at doing a sandbox cleanup when it was migrated from
CVS to SVN. I remember doing a list of dead projects that were still in
sandbox. However, I agree that having a sandbox/{project} dir with at the very
least a README pointing to the new location (for promoted components) would be
useful.
[EMAIL PROTECTED] wrote:
Hi,
The moving from sandbox to proper wiki page needs updating, as it is
all CVS based.
http://wiki.apache.org/jakarta-commons/MovingFromSandboxToProper
The main question that needs resolving is:
* should the code be MOVED from sandbox to proper, or COPIED?
Moving the code means that links to the old location break. But copying
the code means that links to the old stuff don't give any indication
that the main development is now happening elsewhere.
What do people think the best practice is for sandbox-proper promotion?
I think my preference would be
* move the existing code to {proj}/tags/sandbox
* copy to {proj}/trunk
* create a new sandbox/{proj} directory, containing just a README
that points to the new project.
That way, all the sandbox code vanishes from its old location, avoiding
any confusion. But users of the sandbox stuff at least get a hint where
the new stuff is.
The main disadvantage is clutter left in the sandbox directory.
Thoughts?
Regards,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
_
Sign up for eircom broadband now and get a free two month trial.*
Phone 1850 73 00 73 or visit http://home.eircom.net/broadbandoffer
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: moving code from sandbox to proper - best practice?
Good question. We did look at doing a sandbox cleanup when it was migrated from
CVS to SVN. I remember doing a list of dead projects that were still in
sandbox. However, I agree that having a sandbox/{project} dir with at the very
least a README pointing to the new location (for promoted components) would be
useful.
[EMAIL PROTECTED] wrote:
Hi,
The moving from sandbox to proper wiki page needs updating, as it is
all CVS based.
http://wiki.apache.org/jakarta-commons/MovingFromSandboxToProper
The main question that needs resolving is:
* should the code be MOVED from sandbox to proper, or COPIED?
Moving the code means that links to the old location break. But copying
the code means that links to the old stuff don't give any indication
that the main development is now happening elsewhere.
What do people think the best practice is for sandbox-proper promotion?
I think my preference would be
* move the existing code to {proj}/tags/sandbox
* copy to {proj}/trunk
* create a new sandbox/{proj} directory, containing just a README
that points to the new project.
That way, all the sandbox code vanishes from its old location, avoiding
any confusion. But users of the sandbox stuff at least get a hint where
the new stuff is.
The main disadvantage is clutter left in the sandbox directory.
Thoughts?
Regards,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
_
Sign up for eircom broadband now and get a free two month trial.*
Phone 1850 73 00 73 or visit http://home.eircom.net/broadbandoffer
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
