Re: Ex: [DISCUSS] Towards release 0.4.5a56
I suggest doing the simplest thing. Generally the simplest thing is to do one release from each git repository, so that you can say release x.y.z is made from commit abcd1234, you can make the release from one directory, and when you have CI there's only one CI job to validate the software. (I don't know the rationale for splitting into separate git repositories. If the rationale was to decouple the versions in the repositories then separate releases makes sense, because you might want the release schedules to drift apart in future, and you don't want something that is one tarball today become 2 or 3 tarballs in future.) And for the first ASF release, while you're debugging the process, pick just one repository. You can always repeat the process on the other two repositories a week later. Julian On Wed, Nov 2, 2022 at 4:13 PM Frank Greguska wrote: > > I believe we settled on 3 artifacts: > > apache/sdap-nexus-webapp > apache/sdap-collection-manager > apache/sdap-granule-ingester > > There was still some active discussion on if these should share a version > number or not. For sake of argument, let's say they do. > > So tarball would be something like > >- apache-sdapv1.0.0 > - sdap-nexus-webapp > - source code > - sdap-collection-manager > - source code > - sdap-granule-ingester > - source code > > > Github repos would all have v1.0.0 tags/releases > Docker repos would all have v1.0.0 tag > > On Wed, Nov 2, 2022 at 3:52 PM Riley K. Kuttruff wrote: > > > Will there be a tarball corresponding to the Nexus & Ingester repos or > > will both be consolidated into one tatball? > > > > Sent from my Verizon, Samsung Galaxy smartphone > > Get Outlook for Android<https://aka.ms/AAb9ysg> > > ____________ > > From: Perez, Stepheny K (US 398F) > > Sent: Wednesday, November 2, 2022 3:47:25 PM > > To: dev@sdap.apache.org > > Subject: Ex: [DISCUSS] Towards release 0.4.5a56 > > > > 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 > > CAUTION: This email was not sent from a Cal Poly Pomona service. Exercise > > caution when clicking links or opening attachments. Please forward > > suspicious email to suspectem...@cpp.edu<mailto:suspectem...@cpp.edu>. > > > >
Re: [EXTERNAL] Re: Ex: [DISCUSS] Towards release 0.4.5a56
I think the granule ingester and collection manager have some common code components so it might make more sense for something like: -apache-sdapv1.0.0 -sdap-nexus-webapp -src -sdap-ingester -common -src -sdap-collection-manager -src -sdap-granule-ingester -src On 11/2/22, 4:14 PM, "Frank Greguska" wrote: I believe we settled on 3 artifacts: apache/sdap-nexus-webapp apache/sdap-collection-manager apache/sdap-granule-ingester There was still some active discussion on if these should share a version number or not. For sake of argument, let's say they do. So tarball would be something like - apache-sdapv1.0.0 - sdap-nexus-webapp - source code - sdap-collection-manager - source code - sdap-granule-ingester - source code Github repos would all have v1.0.0 tags/releases Docker repos would all have v1.0.0 tag On Wed, Nov 2, 2022 at 3:52 PM Riley K. Kuttruff wrote: > Will there be a tarball corresponding to the Nexus & Ingester repos or > will both be consolidated into one tatball? > > Sent from my Verizon, Samsung Galaxy smartphone > Get Outlook for Android<https://urldefense.us/v3/__https://aka.ms/AAb9ysg__;!!PvBDto6Hs4WbVuu7!ZRMOIRLeE1hNPtw9WaB5AvV0X9BaBL--SoWU92C5qURBd0xg3VmoN3fyYOAla-2hENc$ > > > From: Perez, Stepheny K (US 398F) > Sent: Wednesday, November 2, 2022 3:47:25 PM > To: dev@sdap.apache.org > Subject: Ex: [DISCUSS] Towards release 0.4.5a56 > > 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 > CAUTION: This email was not sent from a Cal Poly Pomona service. Exercise > caution when clicking links or opening attachments. Please forward > suspicious email to suspectem...@cpp.edu<mailto:suspectem...@cpp.edu>. > >
Re: Ex: [DISCUSS] Towards release 0.4.5a56
I believe we settled on 3 artifacts: apache/sdap-nexus-webapp apache/sdap-collection-manager apache/sdap-granule-ingester There was still some active discussion on if these should share a version number or not. For sake of argument, let's say they do. So tarball would be something like - apache-sdapv1.0.0 - sdap-nexus-webapp - source code - sdap-collection-manager - source code - sdap-granule-ingester - source code Github repos would all have v1.0.0 tags/releases Docker repos would all have v1.0.0 tag On Wed, Nov 2, 2022 at 3:52 PM Riley K. Kuttruff wrote: > Will there be a tarball corresponding to the Nexus & Ingester repos or > will both be consolidated into one tatball? > > Sent from my Verizon, Samsung Galaxy smartphone > Get Outlook for Android<https://aka.ms/AAb9ysg> > > From: Perez, Stepheny K (US 398F) > Sent: Wednesday, November 2, 2022 3:47:25 PM > To: dev@sdap.apache.org > Subject: Ex: [DISCUSS] Towards release 0.4.5a56 > > 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 > CAUTION: This email was not sent from a Cal Poly Pomona service. Exercise > caution when clicking links or opening attachments. Please forward > suspicious email to suspectem...@cpp.edu<mailto:suspectem...@cpp.edu>. > >
Re: Ex: [DISCUSS] Towards release 0.4.5a56
Will there be a tarball corresponding to the Nexus & Ingester repos or will both be consolidated into one tatball? Sent from my Verizon, Samsung Galaxy smartphone Get Outlook for Android<https://aka.ms/AAb9ysg> From: Perez, Stepheny K (US 398F) Sent: Wednesday, November 2, 2022 3:47:25 PM To: dev@sdap.apache.org Subject: Ex: [DISCUSS] Towards release 0.4.5a56 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 CAUTION: This email was not sent from a Cal Poly Pomona service. Exercise caution when clicking links or opening attachments. Please forward suspicious email to suspectem...@cpp.edu<mailto:suspectem...@cpp.edu>.