The SVN repo is https://dist.apache.org/repos/dist/dev/incubator/ariatosca/ So you would just check in your change via SVN.
On 2017-12-07 11:22, Thomas Nadeau <tnadeaua...@gmail.com> wrote: > Question about the instructions. It says: > > If this is your first time creating a release for ARIA, make sure to update > the KEYS file > <https://dist.apache.org/repos/dist/dev/incubator/ariatosca/KEYS> with your > key > > > I went ahead and generated a new key, and amended it to the KEYS file that > I found at the URL above which is located here: > > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/KEYS > > I have stored locally. > > How does one modify the actual file in the release area? The release > script that we have doesn't take it as an argument when it pushes the other > artifacts. > > --Tom > > > > > On Thu, Dec 7, 2017 at 5:14 PM, John D. Ament <johndam...@apache.org> wrote: > > > Thomas, > > > > I believe the release process was documented on confluence by prior release > > manager. > > https://cwiki.apache.org/confluence/display/ARIATOSCA/Release+Process > > > > John > > > > On Thu, Dec 7, 2017 at 7:30 AM Thomas Nadeau <tnadeaua...@gmail.com> > > wrote: > > > > > Community, > > > > > > At last week's grooming we agreed that I would invoke the next release of > > > Aria (.3) after certain critical PRs were merged. We are at that time > > now, > > > so I wanted to begin the process. That leads me to my next question... > > > > > > Mentors: is there a document describing the steps to take? There is a > > > script in our repository under releases that appears to have all the > > steps > > > for creating all of our release candidate artifacts, but I am unsure if I > > > need to have the committers/PMCC vote before that is created, afterwards > > or > > > both. I also believe that the apache full PMC is supposed to have some > > > time to review the release candidate too. > > > > > > Thanks, > > > > > > --Tom > > > > > >
