You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@quickstep.apache.org by Jignesh Patel <jm...@gmail.com> on 2016/12/03 00:01:19 UTC
Working towards a release
Hi guys,
I’d like to propose that we start thinking about a release.
A key issue is that we need to figure out how we want to deal with outstanding issues. There is one critical issue (PlanVisualizer related crash). I propose that once that we have that solved, we go forward with the release? Comments?
The guidelines for a release are at: https://incubator.apache.org/guides/release.html The list that we need to go through is:
1.1 Checksums and PGP signatures are valid. See the Release Signing dev documentation.
2.1 Build is successful including automated tests. The expanded source archive is expected to build and pass tests.
3.1 DISCLAIMER is correct, filenames include "incubating". See the Podling Branding Guide.
3.2 Top-level LICENSE and NOTICE are correct for each distribution. See the Licensing How-To, plus various pages under Legal Affairs.
3.3 All source files have license headers where appropriate. See the ASF Source Header and Copyright Notice Policy.
3.4 The provenance of all source files is clear (ASF or software grants). See the IP clearance section of the Mentor's guide, as well as the Releases section of the Incubator's policy page.
3.5 Dependencies licenses are ok as per http://apache.org/legal/ See ASF Legal Previously Asked Questions.
3.6 Release consists of source code only, no binaries. Each Apache release must contain a source package. This package may not contain compiled components (such as "jar" files) because compiled components are not open source, even if they were built from open source.
Would love to get volunteers to help on the items above. If you want to volunteer, let this group know. I can start on items 3.1 – 3.4.
Cheers,
Jignesh
Re: Working towards a release
Posted by Jignesh Patel <jm...@gmail.com>.
Marc:
That is great! Would be great to just write a post about what Quickstep is, what it can do, and how someone can give it a spin.
Cheers,
Jignesh
On 12/4/16, 9:46 AM, "Marc Spehlmann" <sp...@gmail.com> wrote:
I know that Julian mentioned writing some blog posts. I'd like to write
one. Maybe we could distill the recent paper, or talk about a specific
component? Or just talk about all the recent improvements which got our
performance way up before the paper.
On Sat, Dec 3, 2016 at 5:04 PM, Jignesh Patel <jm...@gmail.com>
wrote:
> Thanks Harshad for volunteering!
>
> Re. 3.5, I think the generated files are ok.
>
> We can sync up after you come back. Happy Travels.
>
> Cheers,
> Jignesh
>
> On 12/3/16, 7:25 AM, "Harshad Deshmukh" <ha...@cs.wisc.edu> wrote:
>
> A question on 3.5 - We have preprocessed parser and lexer files in the
> parser module. Should we remove them?
>
>
>
>
>
Re: Working towards a release
Posted by Jignesh Patel <jm...@gmail.com>.
Thanks Hakan!
On 12/11/16, 12:52 AM, "Hakan Memisoglu" <ha...@apache.org> wrote:
Hi Jignesh,
No objections. I can also help you with that.
On 12/10/2016 05:54 PM, Jignesh Patel wrote:
> Fellow Quickstep-pers: AFAIK we are good on all the items under 3.X in the release guidelines at: https://incubator.apache.org/guides/release.html
>
>
>
> Next step, Section 1.1. We need a list of release managers. The reasons for signing a release are listed at: http://www.apache.org/dev/release-signing.html#motivation, and summarized as: “… users can make sure that what they received has not been modified in any way …“
>
>
>
> We need to create a file that contains “… the public key signatures of the release managers (and optionally other committers) for the project …”
>
>
>
> I’m tossing my had in to be part of this group of release managers. Any objections?
>
>
>
> Anyone else wants to join the list of release managers? The more the merrier, and some groups have many of the active committers sign.
>
>
>
> Cheers,
>
> Jignesh
>
>
>
> On 12/4/16, 9:46 AM, "Marc Spehlmann" <sp...@gmail.com> wrote:
>
>
>
> I know that Julian mentioned writing some blog posts. I'd like to write
>
> one. Maybe we could distill the recent paper, or talk about a specific
>
> component? Or just talk about all the recent improvements which got our
>
> performance way up before the paper.
>
>
>
>
>
>
>
> On Sat, Dec 3, 2016 at 5:04 PM, Jignesh Patel <jm...@gmail.com>
>
> wrote:
>
>
>
> > Thanks Harshad for volunteering!
>
> >
>
> > Re. 3.5, I think the generated files are ok.
>
> >
>
> > We can sync up after you come back. Happy Travels.
>
> >
>
> > Cheers,
>
> > Jignesh
>
> >
>
> > On 12/3/16, 7:25 AM, "Harshad Deshmukh" <ha...@cs.wisc.edu> wrote:
>
> >
>
> > A question on 3.5 - We have preprocessed parser and lexer files in the
>
> > parser module. Should we remove them?
>
>
Re: Working towards a release
Posted by Hakan Memisoglu <ha...@apache.org>.
Hi Jignesh,
No objections. I can also help you with that.
On 12/10/2016 05:54 PM, Jignesh Patel wrote:
> Fellow Quickstep-pers: AFAIK we are good on all the items under 3.X in the release guidelines at: https://incubator.apache.org/guides/release.html
>
>
>
> Next step, Section 1.1. We need a list of release managers. The reasons for signing a release are listed at: http://www.apache.org/dev/release-signing.html#motivation, and summarized as: \u201c\u2026 users can make sure that what they received has not been modified in any way \u2026\u201c
>
>
>
> We need to create a file that contains \u201c\u2026 the public key signatures of the release managers (and optionally other committers) for the project \u2026\u201d
>
>
>
> I\u2019m tossing my had in to be part of this group of release managers. Any objections?
>
>
>
> Anyone else wants to join the list of release managers? The more the merrier, and some groups have many of the active committers sign.
>
>
>
> Cheers,
>
> Jignesh
>
>
>
> On 12/4/16, 9:46 AM, "Marc Spehlmann" <sp...@gmail.com> wrote:
>
>
>
> I know that Julian mentioned writing some blog posts. I'd like to write
>
> one. Maybe we could distill the recent paper, or talk about a specific
>
> component? Or just talk about all the recent improvements which got our
>
> performance way up before the paper.
>
>
>
>
>
>
>
> On Sat, Dec 3, 2016 at 5:04 PM, Jignesh Patel <jm...@gmail.com>
>
> wrote:
>
>
>
> > Thanks Harshad for volunteering!
>
> >
>
> > Re. 3.5, I think the generated files are ok.
>
> >
>
> > We can sync up after you come back. Happy Travels.
>
> >
>
> > Cheers,
>
> > Jignesh
>
> >
>
> > On 12/3/16, 7:25 AM, "Harshad Deshmukh" <ha...@cs.wisc.edu> wrote:
>
> >
>
> > A question on 3.5 - We have preprocessed parser and lexer files in the
>
> > parser module. Should we remove them?
>
>
Re: Working towards a release
Posted by Harshad Deshmukh <ha...@cs.wisc.edu>.
Hi Jignesh,
I can volunteer for the release manager role.
On 12/10/2016 05:54 PM, Jignesh Patel wrote:
> Fellow Quickstep-pers: AFAIK we are good on all the items under 3.X in the release guidelines at: https://incubator.apache.org/guides/release.html
>
>
>
> Next step, Section 1.1. We need a list of release managers. The reasons for signing a release are listed at: http://www.apache.org/dev/release-signing.html#motivation, and summarized as: \u201c\u2026 users can make sure that what they received has not been modified in any way \u2026\u201c
>
>
>
> We need to create a file that contains \u201c\u2026 the public key signatures of the release managers (and optionally other committers) for the project \u2026\u201d
>
>
>
> I\u2019m tossing my had in to be part of this group of release managers. Any objections?
>
>
>
> Anyone else wants to join the list of release managers? The more the merrier, and some groups have many of the active committers sign.
>
>
>
> Cheers,
>
> Jignesh
>
>
>
> On 12/4/16, 9:46 AM, "Marc Spehlmann" <sp...@gmail.com> wrote:
>
>
>
> I know that Julian mentioned writing some blog posts. I'd like to write
>
> one. Maybe we could distill the recent paper, or talk about a specific
>
> component? Or just talk about all the recent improvements which got our
>
> performance way up before the paper.
>
>
>
>
>
>
>
> On Sat, Dec 3, 2016 at 5:04 PM, Jignesh Patel <jm...@gmail.com>
>
> wrote:
>
>
>
> > Thanks Harshad for volunteering!
>
> >
>
> > Re. 3.5, I think the generated files are ok.
>
> >
>
> > We can sync up after you come back. Happy Travels.
>
> >
>
> > Cheers,
>
> > Jignesh
>
> >
>
> > On 12/3/16, 7:25 AM, "Harshad Deshmukh" <ha...@cs.wisc.edu> wrote:
>
> >
>
> > A question on 3.5 - We have preprocessed parser and lexer files in the
>
> > parser module. Should we remove them?
>
>
--
Thanks,
Harshad
Re: Working towards a release
Posted by Jignesh Patel <jm...@gmail.com>.
Fellow Quickstep-pers: AFAIK we are good on all the items under 3.X in the release guidelines at: https://incubator.apache.org/guides/release.html
Next step, Section 1.1. We need a list of release managers. The reasons for signing a release are listed at: http://www.apache.org/dev/release-signing.html#motivation, and summarized as: “… users can make sure that what they received has not been modified in any way …“
We need to create a file that contains “… the public key signatures of the release managers (and optionally other committers) for the project …”
I’m tossing my had in to be part of this group of release managers. Any objections?
Anyone else wants to join the list of release managers? The more the merrier, and some groups have many of the active committers sign.
Cheers,
Jignesh
On 12/4/16, 9:46 AM, "Marc Spehlmann" <sp...@gmail.com> wrote:
I know that Julian mentioned writing some blog posts. I'd like to write
one. Maybe we could distill the recent paper, or talk about a specific
component? Or just talk about all the recent improvements which got our
performance way up before the paper.
On Sat, Dec 3, 2016 at 5:04 PM, Jignesh Patel <jm...@gmail.com>
wrote:
> Thanks Harshad for volunteering!
>
> Re. 3.5, I think the generated files are ok.
>
> We can sync up after you come back. Happy Travels.
>
> Cheers,
> Jignesh
>
> On 12/3/16, 7:25 AM, "Harshad Deshmukh" <ha...@cs.wisc.edu> wrote:
>
> A question on 3.5 - We have preprocessed parser and lexer files in the
> parser module. Should we remove them?
Re: Working towards a release
Posted by Marc Spehlmann <sp...@gmail.com>.
I know that Julian mentioned writing some blog posts. I'd like to write
one. Maybe we could distill the recent paper, or talk about a specific
component? Or just talk about all the recent improvements which got our
performance way up before the paper.
On Sat, Dec 3, 2016 at 5:04 PM, Jignesh Patel <jm...@gmail.com>
wrote:
> Thanks Harshad for volunteering!
>
> Re. 3.5, I think the generated files are ok.
>
> We can sync up after you come back. Happy Travels.
>
> Cheers,
> Jignesh
>
> On 12/3/16, 7:25 AM, "Harshad Deshmukh" <ha...@cs.wisc.edu> wrote:
>
> A question on 3.5 - We have preprocessed parser and lexer files in the
> parser module. Should we remove them?
>
>
>
>
>
Re: Working towards a release
Posted by Jignesh Patel <jm...@gmail.com>.
Thanks Harshad for volunteering!
Re. 3.5, I think the generated files are ok.
We can sync up after you come back. Happy Travels.
Cheers,
Jignesh
On 12/3/16, 7:25 AM, "Harshad Deshmukh" <ha...@cs.wisc.edu> wrote:
A question on 3.5 - We have preprocessed parser and lexer files in the parser module. Should we remove them?
Re: Working towards a release
Posted by Harshad Deshmukh <ha...@cs.wisc.edu>.
Hi Jignesh,
I can volunteer. However, I am travelling until the 12th of this month. I can start working once I am back.
A question on 3.5 - We have preprocessed parser and lexer files in the parser module. Should we remove them?
Get Outlook for Android<https://aka.ms/ghei36>
From: Jignesh Patel
Sent: Friday, December 2, 6:02 PM
Subject: Working towards a release
To: dev@quickstep.incubator.apache.org
Hi guys, I'd like to propose that we start thinking about a release. A key issue is that we need to figure out how we want to deal with outstanding issues. There is one critical issue (PlanVisualizer related crash). I propose that once that we have that solved, we go forward with the release? Comments? The guidelines for a release are at: https://incubator.apache.org/guides/release.html The list that we need to go through is: 1.1 Checksums and PGP signatures are valid. See the Release Signing dev documentation. 2.1 Build is successful including automated tests. The expanded source archive is expected to build and pass tests. 3.1 DISCLAIMER is correct, filenames include "incubating". See the Podling Branding Guide. 3.2 Top-level LICENSE and NOTICE are correct for each distribution. See the Licensing How-To, plus various pages under Legal Affairs. 3.3 All source files have license headers where appropriate. See the ASF Source Header and Copyright Notice Policy. 3.4 The provenance of all source files is clear (ASF or software grants). See the IP clearance section of the Mentor's guide, as well as the Releases section of the Incubator's policy page. 3.5 Dependencies licenses are ok as per http://apache.org/legal/ See ASF Legal Previously Asked Questions. 3.6 Release consists of source code only, no binaries. Each Apache release must contain a source package. This package may not contain compiled components (such as "jar" files) because compiled components are not open source, even if they were built from open source. Would love to get volunteers to help on the items above. If you want to volunteer, let this group know. I can start on items 3.1 - 3.4. Cheers, Jignesh