Re: Time for a new release

[John D. Ament]

No, you just commit the file.  There is no other process.

On Mon, Dec 11, 2017 at 9:06 AM Thomas Nadeau  wrote:

>
> Thanks for the pointer.
>
> Is there any sort of pull request process for approvals or are
> these pushes just directly to the master branch?
>
> —Tom
>
>
> > On Dec 9, 2017, at 10:31 AM, John D. Ament 
> wrote:
> >
> > 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  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
> >>  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 
> 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 
> >>> 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
> 
> >>>
> >>
>
>

Re: Time for a new release

[Thomas Nadeau]

Thanks for the pointer. 

Is there any sort of pull request process for approvals or are these 
pushes just directly to the master branch?

—Tom


> On Dec 9, 2017, at 10:31 AM, John D. Ament  wrote:
> 
> 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  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
>>  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  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 
>>> 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
 
>>> 
>> 

Re: Time for a new release

[John D. Ament]

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  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
>  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  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 
> > 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
> > >
> >
> 

Re: Time for a new release

[Thomas Nadeau]

Question about the instructions. It says:

If this is your first time creating a release for ARIA, make sure to update
the KEYS file
 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  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 
> 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
> >
>

Re: Time for a new release

[Thomas Nadeau]

Got it. Thanks. Ill follow those instructions and get this kicked off.

--Tom


On Thu, Dec 7, 2017 at 5:14 PM, John D. Ament  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 
> 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
> >
>

Re: Time for a new release

[Thomas Nadeau]

I added the report to the confluence wiki here:

https://cwiki.apache.org/confluence/display/ARIATOSCA/Podling+Report+2017-DEC-12



On Thu, Dec 7, 2017 at 5:14 PM, John D. Ament  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 
> 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
> >
>

Re: Time for a new release

[Thomas Nadeau]

The doc is done.  Can you please take a look [see link below]?

Also, is there a final resting place for the document other than the 
Confluence Wiki?

—Tom


> On Dec 7, 2017, at 5:14 PM, John D. Ament  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  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
>> 

Time for a new release

[Thomas Nadeau]

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