Re: [EXTERNAL] [VOTE] Release Apache SDAP (incubating) 1.0.0-rc2

[Perez, Stepheny K (US 398F)]

This release is working well for me. +1.


From: Nga Chung 
Sent: Tuesday, December 13, 2022 11:10 AM
To: dev@sdap.apache.org 
Subject: [EXTERNAL] [VOTE] Release Apache SDAP (incubating) 1.0.0-rc2

Hi all,

This is the second release candidate of Apache SDAP (incubating) version
1.0.0.

Changes made between previous candidate (rc1) and this one (rc2) are as
follows:
- Added README
- Added DISCLAIMER

Instructions for building docker images from source can be found here:
https://urldefense.us/v3/__https://incubator-sdap-nexus.readthedocs.io/en/latest/build.html__;!!PvBDto6Hs4WbVuu7!a8nUi_smQN818mWuAEPnw5cIK4sVjNaqWGy47tW1JMb-0EJdftv6755yunjZlymzT1rKYSXxpmw$
Instructions for deploying locally to test can be found here:
https://urldefense.us/v3/__https://incubator-sdap-nexus.readthedocs.io/en/latest/quickstart.html__;!!PvBDto6Hs4WbVuu7!a8nUi_smQN818mWuAEPnw5cIK4sVjNaqWGy47tW1JMb-0EJdftv6755yunjZlymzT1rKphBkEF8$

The tags to be voted on are 1.0.0-rc2:

https://urldefense.us/v3/__https://github.com/apache/incubator-sdap-nexusproto/tree/1.0.0-rc2__;!!PvBDto6Hs4WbVuu7!a8nUi_smQN818mWuAEPnw5cIK4sVjNaqWGy47tW1JMb-0EJdftv6755yunjZlymzT1rKF0EW64U$
https://urldefense.us/v3/__https://github.com/apache/incubator-sdap-ingester/tree/1.0.0-rc2__;!!PvBDto6Hs4WbVuu7!a8nUi_smQN818mWuAEPnw5cIK4sVjNaqWGy47tW1JMb-0EJdftv6755yunjZlymzT1rKxmhlaSc$
https://urldefense.us/v3/__https://github.com/apache/incubator-sdap-nexus/tree/1.0.0-rc2__;!!PvBDto6Hs4WbVuu7!a8nUi_smQN818mWuAEPnw5cIK4sVjNaqWGy47tW1JMb-0EJdftv6755yunjZlymzT1rKUEr4BgY$

The release files, including signatures, digests, etc. can be found at:
https://urldefense.us/v3/__https://dist.apache.org/repos/dist/dev/incubator/sdap/apache-sdap-1.0.0-rc2/__;!!PvBDto6Hs4WbVuu7!a8nUi_smQN818mWuAEPnw5cIK4sVjNaqWGy47tW1JMb-0EJdftv6755yunjZlymzT1rKnXyvhrk$

Release artifacts are signed with the following key:
https://urldefense.us/v3/__https://keyserver.ubuntu.com/pks/lookup?op=get=0xD2449E0EB5EF1E73__;!!PvBDto6Hs4WbVuu7!a8nUi_smQN818mWuAEPnw5cIK4sVjNaqWGy47tW1JMb-0EJdftv6755yunjZlymzT1rKdFIqqj8$

Please vote on releasing this package as Apache SDAP (incubating) 1.0.0.

The vote is open for 72 hours and passes if at least 3 +1 PMC votes are
cast.

[ ] +1 Release this package as Apache SDAP (incubating) 1.0.0
[ ] +0 No opinion
[ ] -1 Do not release this package because ...

Thanks,
Nga

Re: [EXTERNAL] Re: [DISCUSS] Towards release 0.4.5a56

[Perez, Stepheny K (US 398F)]

his directory structure.
> >
> > Let’s look at the artifacts that were in Calcite’s last release. In
> the
> > directory
> >
> https://urldefense.us/v3/__https://dist.apache.org/repos/dist/dev/calcite/apache-calcite-1.31.0-rc2/__;!!PvBDto6Hs4WbVuu7!aY2tIy4CD6wRO7JlwQ9_XSOpDkqvhu8QMq2ROLe907bKV-UqYPygNoR8NjtGkK8Q9VQ$<https://urldefense.us/v3/__https:/dist.apache.org/repos/dist/dev/calcite/apache-calcite-1.31.0-rc2/__;!!PvBDto6Hs4WbVuu7!aY2tIy4CD6wRO7JlwQ9_XSOpDkqvhu8QMq2ROLe907bKV-UqYPygNoR8NjtGkK8Q9VQ$>
> > sh
> > you’ll see the following files:
> >
> >  * apache-calcite-1.31.0-src.tar.gz # source tar ball
> >  * apache-calcite-1.31.0-src.tar.gz.asc # armored signature
> generated by
> > PGP
> >  * apache-calcite-1.31.0-src.tar.gz.sha512 # SHA512 checksum of the
> > src.tar.gz file
> >
> > SDAP will need equivalent files.
> >
> > Now, how to write to dist.apache.org? That web server is a view
> onto an
> > ASF
> > source code repository managed by the Subversion source control
> system. ASF
> > uses it for content management of releases.
> >
> > First, install subversion. "sudo apt-get install subversion” or
> similar.
> >
> > Then checkout the tree:
> >
> >   svn co
> https://urldefense.us/v3/__https://dist.apache.org/repos/dist/dev/incubator/sdap/trunk__;!!PvBDto6Hs4WbVuu7!aY2tIy4CD6wRO7JlwQ9_XSOpDkqvhu8QMq2ROLe907bKV-UqYPygNoR8NjtGTWMmcJY$<https://urldefense.us/v3/__https:/dist.apache.org/repos/dist/dev/incubator/sdap/trunk__;!!PvBDto6Hs4WbVuu7!aY2tIy4CD6wRO7JlwQ9_XSOpDkqvhu8QMq2ROLe907bKV-UqYPygNoR8NjtGTWMmcJY$>
> sdap
> >   cd sdap
> >   mkdir apache-sdap-0.4.5a56-rc0
> >
> > Create some files, then check them in:
> >
> >   svn add apache-sdap-0.4.5a56-rc0
> >   svn ci -m’Uploading release candidate Apache SDAP
> sdap-0.4.5a56-rc0 to
> > dev area’ apache-sdap-0.4.5a56-rc0
> >
> > These instructions are from memory, so there might be a few mistakes.
> > Hopefully you get the general idea. Do some Google searches and
> you’ll
> > probably find the release instructions used by other projects.
> >
> > You'll need to log into subversion using your ASF username and
> password,
> > but I don’t remember the details.
> >
> > Be sure to write a ‘how to’ so that the next release manager can
> follow
> > your steps, and add it to the source code when you’re done. And
> maybe one
> > or two shell scripts.
> >
> > I also recommend that you create a bug with the title ‘Release SDAP
> > 0.4.5a56’. It will be a useful place to have discussions, link to
> other
> > bugs, release notes, etc.
> >
> > Julian
> >
> >
> > On Nov 9, 2022, at 3:32 PM, Nga Chung  wrote:
> >
> > I'm going to be the release manager for this first release. Where
> exactly
> > do we upload the 3 .tar.gz (1 per repository) to?
> >
> > Thanks,
> > Nga
> >
> > On Thu, Nov 3, 2022 at 5:12 PM Julian Hyde  wrote:
> >
> > Regarding testing. I recommend that the release manager creates a
> > recipe ("HOWTO") for the steps to create a release. One of those
> steps
> > is a manual smoke test (e.g. am I able to start the server and do x,
> > y, and z simple operations).
> >
> > Other people voting on the release can do their own smoke tests.
> >
> > But do bear in mind that if there are bugs, this does not prevent a
> > release. Clearly you don't want show-stopper bugs like code that
> > doesn't compile.
> >
> > Julian
> >
> >
> > On Wed, Nov 2, 2022 at 3:47 PM Perez, Stepheny K (US 398F)
> >  wrote:
> >
> >
> > Hi everyone,
> >
> > I’d like to start the conversation regarding our first official
> Apache
> >
> > release. From what I can tell, these are the major items that need
> to be
> > completed before we can move forward:
> >
> >
> >
> > 1.   Identify a release manager. Any volunteers?
> >
> > 2.   Create release tarball
> >
> > 3.   Write release notes
> >
> > 4.   Write installation instructions from source (Riley Kuttruff
> has
> >
> > started this work)
> >
> >
> > 5.   Push docker images to Dockerhub (and update quickstart with
> >
> > these versions)
> >
> >
> > Another important task before moving forward would be testing the
> latest
> >
> > SDAP analysis image 0.4.5a56. I have personally used this version
> without
> > any issues. Has anyone else upgraded to this latest alpha version?
> >
> >
> > Thank you!
> > Stepheny
> >
>
>

[DISCUSS] Towards release 0.4.5a56

[Perez, Stepheny K (US 398F)]

Hi everyone,

I’d like to start the conversation regarding our first official Apache release. 
From what I can tell, these are the major items that need to be completed 
before we can move forward:


1.   Identify a release manager. Any volunteers?

2.   Create release tarball

3.   Write release notes

4.   Write installation instructions from source (Riley Kuttruff has 
started this work)

5.   Push docker images to Dockerhub (and update quickstart with these 
versions)

Another important task before moving forward would be testing the latest SDAP 
analysis image 0.4.5a56. I have personally used this version without any 
issues. Has anyone else upgraded to this latest alpha version?

Thank you!
Stepheny

Re: [EXTERNAL] November Apache SDAP report draft

[Perez, Stepheny K (US 398F)]

I removed the release from the report. I’ll also start that conversation 
regarding release 0.4.5a56. Thanks again!

Stepheny

From: Julian Hyde 
Date: Wednesday, November 2, 2022 at 1:20 PM
To: dev@sdap.apache.org 
Subject: Re: [EXTERNAL] November Apache SDAP report draft
It’s not a release for Apache’s purposes because it hasn’t been through the 
signing/vote/publish/announce process. An Apache release is a legal and 
community action more than it is a piece of code. The software quality of the 
release (e.g. ‘alpha’) is irrelevant to Apache, but the process of creating the 
release is all-important.

Yes, I think you should remove the release from the report. If you do that I’ll 
amend my comments.

I am happy to work with SDAP committers on an Apache-style release. We can 
probably use the 0.4.5a56 tag as a starting point. A good starting point would 
be an email to the dev list with the subject “[DISCUSS] Towards release 
0.4.5a56” asking when would be a good time for a release, volunteer for release 
manager, agree on a list of tasks, etc.

Julian




> On Nov 2, 2022, at 11:38 AM, Perez, Stepheny K (US 398F) 
>  wrote:
>
> Julian,
>
> The release I was referring to in our report was 0.4.5a56 which is an alpha 
> release. Would specifying this in the report make it more accurate? If not, I 
> can remove that from the report altogether. Thanks for your feedback.
>
> Stepheny
>
> From: Julian Hyde 
> Date: Wednesday, November 2, 2022 at 11:22 AM
> To: dev@sdap.apache.org 
> Subject: [EXTERNAL] Re: November Apache SDAP report draft
> Thanks for writing and submitting the report, Stepheny.
>
> I signed off and made the following comments:
>
>> The report says that there has been a release. I dispute
>> that. There is no release vote on dev@, no mention of the
>> release on dev@, nothing on announce@, and no downloads page.
>>
>> As far as I can tell, this project has never made an Apache
>> release.
>>
>> SDAP's number 1 problem is their use of dev@. There is activity
>> in the project (including commit messages going to dev@) but
>> questions asked on dev@ go unanswered, and therefore
>> conversations don't happen. Even the report is drafted on
>> private@ rather than dev@.  I think I can work with SDAP and get
>> them to graduate but only if they engage on dev@.
>>
>> I have given notice that I will resign as a mentor by Dec 31st if
>> I don't see activity, namely a plan to graduate, and activity to
>> carry out that plan.
>
> Julian
>
>
> On 2022/11/02 00:57:44 "Perez, Stepheny K (US 398F)" wrote:
>> Hello,
>>
>> Attached you will find a draft of the November 2022 Apache SDAP report. In 
>> this report, I’ve included details about what steps we still need to take 
>> before graduating and a target date for graduating. Please provide feedback 
>> on the contents, as I’ll be submitting the reporting today at C.O.B.
>>
>> Thank you!
>> Stepheny
>>
>>

Re: [EXTERNAL] Re: November Apache SDAP report draft

[Perez, Stepheny K (US 398F)]

Julian,

The release I was referring to in our report was 0.4.5a56 which is an alpha 
release. Would specifying this in the report make it more accurate? If not, I 
can remove that from the report altogether. Thanks for your feedback.

Stepheny

From: Julian Hyde 
Date: Wednesday, November 2, 2022 at 11:22 AM
To: dev@sdap.apache.org 
Subject: [EXTERNAL] Re: November Apache SDAP report draft
Thanks for writing and submitting the report, Stepheny.

I signed off and made the following comments:

> The report says that there has been a release. I dispute
> that. There is no release vote on dev@, no mention of the
> release on dev@, nothing on announce@, and no downloads page.
>
> As far as I can tell, this project has never made an Apache
> release.
>
> SDAP's number 1 problem is their use of dev@. There is activity
> in the project (including commit messages going to dev@) but
> questions asked on dev@ go unanswered, and therefore
> conversations don't happen. Even the report is drafted on
> private@ rather than dev@.  I think I can work with SDAP and get
> them to graduate but only if they engage on dev@.
>
> I have given notice that I will resign as a mentor by Dec 31st if
> I don't see activity, namely a plan to graduate, and activity to
> carry out that plan.

Julian


On 2022/11/02 00:57:44 "Perez, Stepheny K (US 398F)" wrote:
> Hello,
>
> Attached you will find a draft of the November 2022 Apache SDAP report. In 
> this report, I’ve included details about what steps we still need to take 
> before graduating and a target date for graduating. Please provide feedback 
> on the contents, as I’ll be submitting the reporting today at C.O.B.
>
> Thank you!
> Stepheny
>
>

November Apache SDAP report draft

[Perez, Stepheny K (US 398F)]

Hello,

Attached you will find a draft of the November 2022 Apache SDAP report. In this 
report, I’ve included details about what steps we still need to take before 
graduating and a target date for graduating. Please provide feedback on the 
contents, as I’ll be submitting the reporting today at C.O.B.

Thank you!
Stepheny

Re: [EXTERNAL] Re: Podling Sdap Report Reminder - November 2022

[Perez, Stepheny K (US 398F)]

Hi Julian,

I’d like to volunteer to write the report. I’ll send out a draft sometime today.

Thanks for the reminder!
Stepheny

From: Julian Hyde 
Date: Saturday, October 29, 2022 at 3:56 PM
To: dev@sdap.apache.org 
Subject: [EXTERNAL] Re: Podling Sdap Report Reminder - November 2022
The report needs to be submitted in a few days. Is there a volunteer to write 
it?

There has been some discussion about graduation this month. In the report I 
would like to see a plan for how SDAP intends to graduate, and a timeline for 
when that can happen.

As I have said before, I came on board as a mentor to give SDAP a push over the 
finishing line, if that is what it needs. But if the project doesn't want to 
graduate, I can't do anything about that and I will be wasting my time. If I 
don't see a commitment to graduate and active steps to make it happen, I shall 
be gone by Dec 31st.

Julian

On 2022/10/23 04:08:45 jmcl...@apache.org wrote:
> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 16 November 2022.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, November 02).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Candidate names should not be made public before people are actually
> elected, so please do not include the names of potential committers or
> PPMC members in your report.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> --
>
> Your report should contain the following:
>
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> *   A list of the three most important issues to address in the move
> towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
> *   How does the podling rate their own maturity.
>
> This should be appended to the Incubator Wiki page at:
>
> https://urldefense.us/v3/__https://cwiki.apache.org/confluence/display/INCUBATOR/November2022__;!!PvBDto6Hs4WbVuu7!ZwANGT6U0aHfR7IMMMk6gsRBe3zAqF5WPgsE31mKKEdHGXeF7C4ahSGmBElctsAoA1cnYU2GpJU$
>
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
>
> Note: The format of the report has changed to use markdown.
>
> Mentors
> ---
>
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
>
> Incubator PMC
>