You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Bertrand Delacretaz <bd...@codeconsult.ch> on 2019/03/04 16:12:30 UTC
Re: Changes to Website and Marking As Obsolete SVN Version of
Incubator Website
Hi Dave,
On Thu, Feb 28, 2019 at 7:37 PM Dave Fisher <da...@comcast.net> wrote:
> ...I’ve been reviewing the incubator’s svn repository. In order to avoid confusion I am going to
> add README.txt files to directories (eg. [1]) which are now obsolete, but not obviously so....
How about moving them under an OBSOLETE folder instead?
That would make things clearer - just make sure the website build at
https://builds.apache.org/view/H-L/view/Incubator/job/Incubator%20Site/
still works after that.
-Bertrand
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Changes to Website and Marking As Obsolete SVN Version of
Incubator Website
Posted by Greg Stein <gs...@gmail.com>.
On Tue, Mar 5, 2019 at 4:56 AM Bertrand Delacretaz <
bdelacretaz@codeconsult.ch> wrote:
> On Tue, Mar 5, 2019 at 10:04 AM Greg Stein <gs...@gmail.com> wrote:
> > ...So, rather than OBSOLETE, or multiple README, I advocate a single
> top-level
> > README that details the deletions/reasons. Then just do an svn rm...
>
> Works for me, the idea of OBSOLETE is to make it obvious that stuff
> has been deactivated but a clear README works as well.
>
> (erring on the safe side here as I'm not sure if anyone still has the
> overview on what's useful or not)
>
It's a reversible step. Any directory/file can be recovered from history.
No worries.
Re: Changes to Website and Marking As Obsolete SVN Version of
Incubator Website
Posted by Bertrand Delacretaz <bd...@codeconsult.ch>.
On Tue, Mar 5, 2019 at 10:04 AM Greg Stein <gs...@gmail.com> wrote:
> ...So, rather than OBSOLETE, or multiple README, I advocate a single top-level
> README that details the deletions/reasons. Then just do an svn rm...
Works for me, the idea of OBSOLETE is to make it obvious that stuff
has been deactivated but a clear README works as well.
(erring on the safe side here as I'm not sure if anyone still has the
overview on what's useful or not)
-Bertrand
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Changes to Website and Marking As Obsolete SVN Version of
Incubator Website
Posted by Greg Stein <gs...@gmail.com>.
On Mon, Mar 4, 2019 at 10:12 AM Bertrand Delacretaz <
bdelacretaz@codeconsult.ch> wrote:
> Hi Dave,
>
> On Thu, Feb 28, 2019 at 7:37 PM Dave Fisher <da...@comcast.net> wrote:
> > ...I’ve been reviewing the incubator’s svn repository. In order to avoid
> confusion I am going to
> > add README.txt files to directories (eg. [1]) which are now obsolete,
> but not obviously so....
>
> How about moving them under an OBSOLETE folder instead?
With Subversion, the content will always be there. Moving them to an
OBSOLETE folder is kinda silly. Just delete the stuff, so *current*
checkouts don't pick up the content.
A single, top-level README.txt indicating what "significant" directories
were removed, and in what revision ... now *that* would be helpful. It is
somewhat difficult to discover deleted directories in svn, even though
they're sitting right there in history. ... But a README can say "removed
../site/ in r$FOO because we moved our site content over to
$gitRepositoryURL"
So, rather than OBSOLETE, or multiple README, I advocate a single top-level
README that details the deletions/reasons. Then just do an svn rm.
Cheers,
-g