empire-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Francis De Brabandere (JIRA)" <empire-db-...@incubator.apache.org>
Subject [jira] [Created] (EMPIREDB-234) people.apache.org web space is moving to home.apache.org
Date Wed, 25 Nov 2015 15:13:10 GMT
Francis De Brabandere created EMPIREDB-234:

             Summary: people.apache.org web space is moving to home.apache.org
                 Key: EMPIREDB-234
                 URL: https://issues.apache.org/jira/browse/EMPIREDB-234
             Project: Empire-DB
          Issue Type: Task
            Reporter: Francis De Brabandere
            Assignee: Francis De Brabandere
            Priority: Minor

Need to update release guide

Hi folks,
as the subject says, people.apache.org is being decommissioned soon, and
personal web space is being moved to a new home, aptly named
home.apache.org ( https://home.apache.org/ )

If you have things on people.apache.org that you would like to retain,
please make a copy of it and move it to home.apache.org. (note, you will
have to make a folder called 'public_html' there, for items to show up
under https://home.apache.org/~yourID/ ).

We will _NOT_ be moving your data for you. There is simply too much old
junk data on minotaur (the current people.apache.org machine) for it to
make sense to rsync it across, so we have made the decision that moving
data is up to each individual committer.

The new host, home.apache.org, will ONLY be for web space, you will not
have shell access to the machine (but you can copy data to it using SFTP
and your SSH key). Access to modify LDAP records (for project chairs)
will be moved to a separate host when the time comes.

There will be a 3 month grace period to move your data across. After
this time span (March 1st, 2016), minotaur will no longer serve up
personal web space, and visits to people.apache.org will be redirected
to home.apache.org.

With regards,
Daniel on behalf of the Apache Infrastructure Team.

PS: All replies to this should go to infrastructure@apache.org


There is a staging area on the dist server for just this purpose:
Upload the RC to that instead.

This is much better than the home directory on people because there is
no need to copy the files again when the vote succeeds.
Instead you can use svn/svnmucc to move the files to the dist release
directory (same repo, so files don't travel across the network).
Also there can be proper traceability of the RC artifacts; just
include the revision number of the dev tree in the vote e-mail.

This message was sent by Atlassian JIRA

View raw message