[VOTE] Request for Waiver of Make a Release requirement for Incubator graduation
Hello IPMC, The Subversion podling would like a waiver of the requirement to make a release before graduation. As we understand this requirement, it is present in order to demonstrate to the podling how releases are made at the ASF. Packaging, licensing, signing, placement into the distrubtion/mirror system, announcements, among others[1]. We believe that the Subversion community already has a deep understanding of the Apache release model, based on the following qualifications of several of its committers/mentors: * Greg Stein has been a committer at Apache since before the Foundation was started. He has been involved in releases of httpd and APR, including time as Release Manager (RM) for APR. He helped to establish the APR TLP and the Commons TLP (prior incarnation; now defunct). Greg wrote the versioning guidelines for APR, which are also in use by the Subversion project. Through his 8+ years on the Board, he has read and reviewed reports from across the ASF about release, IP, and infrastructure issues. * Justin Erenkrantz has been a committer since 2001, contributing to httpd and APR, along with mentoring the stdcxx project when it was in the Incubator. He has been the RM for both httpd and APR. In fact, Justin wrote the initial guidelines for the release of httpd. Justin has been part of Infrastructure almost since its inception as a distinct group, which includes the provision of all the facilities to actually make and distribute ASF releases. Justin has spent many years on the Board, providing further insight to releases across the Foundation. * Sander Striker has been a committer since 2001, contributing to APR and then httpd. Sander acted as the RM for httpd releases, and also held a stint as the VP for httpd. Add in his time spent with Infrastructure and the Board, and he's been observing ASF releases for many years. * Garrett Rooney has been a committer since 2004, contributing and making releases of APR, and committing to httpd. He was also the VP of APR for several years, and has mentored two Incubating projects. * Daniel Rall has been a committer since 2001, contributing to many projects: Turbine, Fulcrum, Torque, and numerous Jakarta Commons projects. He established the community around XML-RPC, brought it through the Incubator, and maintained it for several years within the XML Project. He also participated in some of the bootstrapping around the Velocity and Maven projects, and participated on the Infra team. The Subversion community's belief is that we have ample experience to guide us in making a release, when that time is arrives. There will certainly be variances (e.g. mirroring) from our current established procedures[2], but some simple fine-tuning should resolve that. The bulk of the existing release process already meets and exceeds that a typical Apache release. Niclas Hedman pointed out that the Subversion community has produced 32 releases over the past four years, which hopefully indicates a smooth, understood, and functional release process. Cheers, -g [1] one particular item is using a release as a gating/focal point for legal review, but we feel that can be performed as an action separate/distinct from performing a release [2] http://subversion.tigris.org/release-process.html - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Request for Waiver of Make a Release requirement for Incubator graduation
Greg Stein wrote: The Subversion podling would like a waiver of the requirement to make a release before graduation. As we understand this requirement, it is present in order to demonstrate to the podling how releases are made at the ASF. Packaging, licensing, signing, placement into the distrubtion/mirror system, announcements, among others[1]. We believe that the Subversion community already has a deep understanding of the Apache release model +1; this checkpoint isn't needed for this specific project. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Request for Waiver of Make a Release requirement for Incubator graduation
On Tue, Nov 10, 2009 at 6:17 PM, Greg Stein gst...@gmail.com wrote: Hello IPMC, The Subversion podling would like a waiver of the requirement to make a release before graduation. As we understand this requirement, it is present in order to demonstrate to the podling how releases are made at the ASF. Packaging, licensing, signing, placement into the distrubtion/mirror system, announcements, among others[1]. We believe that the Subversion community already has a deep understanding of the Apache release model, based on the following qualifications of several of its committers/mentors: * Greg Stein has been a committer at Apache since before the Foundation was started. He has been involved in releases of httpd and APR, including time as Release Manager (RM) for APR. He helped to establish the APR TLP and the Commons TLP (prior incarnation; now defunct). Greg wrote the versioning guidelines for APR, which are also in use by the Subversion project. Through his 8+ years on the Board, he has read and reviewed reports from across the ASF about release, IP, and infrastructure issues. * Justin Erenkrantz has been a committer since 2001, contributing to httpd and APR, along with mentoring the stdcxx project when it was in the Incubator. He has been the RM for both httpd and APR. In fact, Justin wrote the initial guidelines for the release of httpd. Justin has been part of Infrastructure almost since its inception as a distinct group, which includes the provision of all the facilities to actually make and distribute ASF releases. Justin has spent many years on the Board, providing further insight to releases across the Foundation. * Sander Striker has been a committer since 2001, contributing to APR and then httpd. Sander acted as the RM for httpd releases, and also held a stint as the VP for httpd. Add in his time spent with Infrastructure and the Board, and he's been observing ASF releases for many years. * Garrett Rooney has been a committer since 2004, contributing and making releases of APR, and committing to httpd. He was also the VP of APR for several years, and has mentored two Incubating projects. * Daniel Rall has been a committer since 2001, contributing to many projects: Turbine, Fulcrum, Torque, and numerous Jakarta Commons projects. He established the community around XML-RPC, brought it through the Incubator, and maintained it for several years within the XML Project. He also participated in some of the bootstrapping around the Velocity and Maven prtingojects, and participated on the Infra team. The Subversion community's belief is that we have ample experience to guide us in making a release, when that time is arrives. There will certainly be variances (e.g. mirroring) from our current established procedures[2], but some simple fine-tuning should resolve that. The bulk of the existing release process already meets and exceeds that a typical Apache release. Niclas Hedman pointed out that the Subversion community has produced 32 releases over the past four years, which hopefully indicates a smooth, understood, and functional release process. Cheers, -g [1] one particular item is using a release as a gating/focal point for legal review, but we feel that can be performed as an action separate/distinct from performing a release [2] http://subversion.tigris.org/release-process.html -0 I'm not at all familiar with how the Subversion project works so as an IPMC member I don't see how I can decide this before they've even started incubating. This is a graduation issue, why can't it just wait until then and say in the graduation proposal there's not been a release but its not necessary because of x y z. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Request for Waiver of Make a Release requirement for Incubator graduation
On Tue, Nov 10, 2009 at 10:17 AM, Greg Stein gst...@gmail.com wrote: Hello IPMC, The Subversion podling would like a waiver of the requirement to make a release before graduation. As we understand this requirement, it is present in order to demonstrate to the podling how releases are made at the ASF. Packaging, licensing, signing, placement into the distrubtion/mirror system, announcements, among others[1]. We believe that the Subversion community already has a deep understanding of the Apache release model, based on the following qualifications of several of its committers/mentors: Should we hold this vote to actually graduation time ? Would it be better to spend some of these debating energy to actually setup the Subversion podling into the Apache infrastructure, as currently I see no mailing lists, svn code import, etc... create the proper Apache user accounts for the several new committers, etc and maybe still give a chance to add new contributors... before worrying about this... -- Luciano Resende http://people.apache.org/~lresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Request for Waiver of Make a Release requirement for Incubator graduation
- Original Message From: Luciano Resende luckbr1...@gmail.com To: general@incubator.apache.org Sent: Tue, November 10, 2009 10:51:44 AM Subject: Re: [VOTE] Request for Waiver of Make a Release requirement for Incubator graduation On Tue, Nov 10, 2009 at 10:17 AM, Greg Stein wrote: Hello IPMC, The Subversion podling would like a waiver of the requirement to make a release before graduation. As we understand this requirement, it is present in order to demonstrate to the podling how releases are made at the ASF. Packaging, licensing, signing, placement into the distrubtion/mirror system, announcements, among others[1]. We believe that the Subversion community already has a deep understanding of the Apache release model, based on the following qualifications of several of its committers/mentors: Should we hold this vote to actually graduation time ? Would it be better to spend some of these debating energy to actually setup the Subversion podling into the Apache infrastructure, as currently I see no mailing lists, svn code import, etc... create the proper Apache user accounts for the several new committers, etc and maybe still give a chance to add new contributors... before worrying about this... Agreed. Starting the ball rolling by requesting a bunch of waivers is personally off-putting and bureaucratic. Something I'd like to see less off in the Incubator. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Request for Waiver of Make a Release requirement for Incubator graduation
Before graduation, I expect ALL podlings to, at some point, present the Incubator PMC with some artifacts that the podling community feels meets the Apache legal requirements. I don't care if said artifacts are a release or a nightly snapshot or a one off, but I expect to see such artifacts as part of the incubation process. Such review is to ensure that the podling has properly understood the legal bits. That IS part of the Incubator PMC's tasks. I'm not really sure if this is a -1 or a +1. I don't care about an actual release, but I do care about making sure artifacts are presented to the IPMC for complete review prior to graduation. Dan On Tue November 10 2009 1:17:41 pm Greg Stein wrote: Hello IPMC, The Subversion podling would like a waiver of the requirement to make a release before graduation. As we understand this requirement, it is present in order to demonstrate to the podling how releases are made at the ASF. Packaging, licensing, signing, placement into the distrubtion/mirror system, announcements, among others[1]. We believe that the Subversion community already has a deep understanding of the Apache release model, based on the following qualifications of several of its committers/mentors: * Greg Stein has been a committer at Apache since before the Foundation was started. He has been involved in releases of httpd and APR, including time as Release Manager (RM) for APR. He helped to establish the APR TLP and the Commons TLP (prior incarnation; now defunct). Greg wrote the versioning guidelines for APR, which are also in use by the Subversion project. Through his 8+ years on the Board, he has read and reviewed reports from across the ASF about release, IP, and infrastructure issues. * Justin Erenkrantz has been a committer since 2001, contributing to httpd and APR, along with mentoring the stdcxx project when it was in the Incubator. He has been the RM for both httpd and APR. In fact, Justin wrote the initial guidelines for the release of httpd. Justin has been part of Infrastructure almost since its inception as a distinct group, which includes the provision of all the facilities to actually make and distribute ASF releases. Justin has spent many years on the Board, providing further insight to releases across the Foundation. * Sander Striker has been a committer since 2001, contributing to APR and then httpd. Sander acted as the RM for httpd releases, and also held a stint as the VP for httpd. Add in his time spent with Infrastructure and the Board, and he's been observing ASF releases for many years. * Garrett Rooney has been a committer since 2004, contributing and making releases of APR, and committing to httpd. He was also the VP of APR for several years, and has mentored two Incubating projects. * Daniel Rall has been a committer since 2001, contributing to many projects: Turbine, Fulcrum, Torque, and numerous Jakarta Commons projects. He established the community around XML-RPC, brought it through the Incubator, and maintained it for several years within the XML Project. He also participated in some of the bootstrapping around the Velocity and Maven projects, and participated on the Infra team. The Subversion community's belief is that we have ample experience to guide us in making a release, when that time is arrives. There will certainly be variances (e.g. mirroring) from our current established procedures[2], but some simple fine-tuning should resolve that. The bulk of the existing release process already meets and exceeds that a typical Apache release. Niclas Hedman pointed out that the Subversion community has produced 32 releases over the past four years, which hopefully indicates a smooth, understood, and functional release process. Cheers, -g [1] one particular item is using a release as a gating/focal point for legal review, but we feel that can be performed as an action separate/distinct from performing a release [2] http://subversion.tigris.org/release-process.html - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Daniel Kulp dk...@apache.org http://www.dankulp.com/blog - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Request for Waiver of Make a Release requirement for Incubator graduation
On Tue, Nov 10, 2009 at 13:54, Joe Schaefer joe_schae...@yahoo.com wrote: - Original Message From: Luciano Resende luckbr1...@gmail.com To: general@incubator.apache.org Sent: Tue, November 10, 2009 10:51:44 AM Subject: Re: [VOTE] Request for Waiver of Make a Release requirement for Incubator graduation On Tue, Nov 10, 2009 at 10:17 AM, Greg Stein wrote: Hello IPMC, The Subversion podling would like a waiver of the requirement to make a release before graduation. As we understand this requirement, it is present in order to demonstrate to the podling how releases are made at the ASF. Packaging, licensing, signing, placement into the distrubtion/mirror system, announcements, among others[1]. We believe that the Subversion community already has a deep understanding of the Apache release model, based on the following qualifications of several of its committers/mentors: Should we hold this vote to actually graduation time ? Would it be better to spend some of these debating energy to actually setup the Subversion podling into the Apache infrastructure, as currently I see no mailing lists, svn code import, etc... create the proper Apache user accounts for the several new committers, etc and maybe still give a chance to add new contributors... before worrying about this... Agreed. Starting the ball rolling by requesting a bunch of waivers is personally off-putting and bureaucratic. Something I'd like to see less off in the Incubator. /me shrugs Releases are the topic of the day. I wanted to get that whole discussion behind us, and move onto something constructive. Cheers, -g - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Request for Waiver of Make a Release requirement for Incubator graduation
On Tue, Nov 10, 2009 at 13:51, Luciano Resende luckbr1...@gmail.com wrote: On Tue, Nov 10, 2009 at 10:17 AM, Greg Stein gst...@gmail.com wrote: Hello IPMC, The Subversion podling would like a waiver of the requirement to make a release before graduation. As we understand this requirement, it is present in order to demonstrate to the podling how releases are made at the ASF. Packaging, licensing, signing, placement into the distrubtion/mirror system, announcements, among others[1]. We believe that the Subversion community already has a deep understanding of the Apache release model, based on the following qualifications of several of its committers/mentors: Should we hold this vote to actually graduation time ? Would it be better to spend some of these debating energy to actually setup the Subversion podling into the Apache infrastructure, as currently I see no mailing lists, svn code import, etc... create the proper Apache user accounts for the several new committers, etc and maybe still give a chance to add new contributors... before worrying about this... We're three days into incubation. Votes are still running on the form for the repository, which bug tracker, mailing list migration, etc. While that discussion/voting is running, I can deal with some of these other issues dealing with graduation. ICLAs are arriving, the repos should be imported within a couple weeks, and account requests will go out in bulk before then. I'm simply trying to parallelize the many tasks. Cheers, -g - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Request for Waiver of Make a Release requirement for Incubator graduation
I agree with the following, i don't think a waiver is needed right now... This is a graduation issue, why can't it just wait until then and say in the graduation proposal there's not been a release but its not necessary because of x y z. thanks, dims On 11/10/2009 01:49 PM, ant elder wrote: On Tue, Nov 10, 2009 at 6:17 PM, Greg Steingst...@gmail.com wrote: Hello IPMC, The Subversion podling would like a waiver of the requirement to make a release before graduation. As we understand this requirement, it is present in order to demonstrate to the podling how releases are made at the ASF. Packaging, licensing, signing, placement into the distrubtion/mirror system, announcements, among others[1]. We believe that the Subversion community already has a deep understanding of the Apache release model, based on the following qualifications of several of its committers/mentors: * Greg Stein has been a committer at Apache since before the Foundation was started. He has been involved in releases of httpd and APR, including time as Release Manager (RM) for APR. He helped to establish the APR TLP and the Commons TLP (prior incarnation; now defunct). Greg wrote the versioning guidelines for APR, which are also in use by the Subversion project. Through his 8+ years on the Board, he has read and reviewed reports from across the ASF about release, IP, and infrastructure issues. * Justin Erenkrantz has been a committer since 2001, contributing to httpd and APR, along with mentoring the stdcxx project when it was in the Incubator. He has been the RM for both httpd and APR. In fact, Justin wrote the initial guidelines for the release of httpd. Justin has been part of Infrastructure almost since its inception as a distinct group, which includes the provision of all the facilities to actually make and distribute ASF releases. Justin has spent many years on the Board, providing further insight to releases across the Foundation. * Sander Striker has been a committer since 2001, contributing to APR and then httpd. Sander acted as the RM for httpd releases, and also held a stint as the VP for httpd. Add in his time spent with Infrastructure and the Board, and he's been observing ASF releases for many years. * Garrett Rooney has been a committer since 2004, contributing and making releases of APR, and committing to httpd. He was also the VP of APR for several years, and has mentored two Incubating projects. * Daniel Rall has been a committer since 2001, contributing to many projects: Turbine, Fulcrum, Torque, and numerous Jakarta Commons projects. He established the community around XML-RPC, brought it through the Incubator, and maintained it for several years within the XML Project. He also participated in some of the bootstrapping around the Velocity and Maven prtingojects, and participated on the Infra team. The Subversion community's belief is that we have ample experience to guide us in making a release, when that time is arrives. There will certainly be variances (e.g. mirroring) from our current established procedures[2], but some simple fine-tuning should resolve that. The bulk of the existing release process already meets and exceeds that a typical Apache release. Niclas Hedman pointed out that the Subversion community has produced 32 releases over the past four years, which hopefully indicates a smooth, understood, and functional release process. Cheers, -g [1] one particular item is using a release as a gating/focal point for legal review, but we feel that can be performed as an action separate/distinct from performing a release [2] http://subversion.tigris.org/release-process.html -0 I'm not at all familiar with how the Subversion project works so as an IPMC member I don't see how I can decide this before they've even started incubating. This is a graduation issue, why can't it just wait until then and say in the graduation proposal there's not been a release but its not necessary because of x y z. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Request for Waiver of Make a Release requirement for Incubator graduation
- Original Message From: Greg Stein gst...@gmail.com To: general@incubator.apache.org Sent: Tue, November 10, 2009 11:00:07 AM Subject: Re: [VOTE] Request for Waiver of Make a Release requirement for Incubator graduation On Tue, Nov 10, 2009 at 13:54, Joe Schaefer wrote: - Original Message From: Luciano Resende To: general@incubator.apache.org Sent: Tue, November 10, 2009 10:51:44 AM Subject: Re: [VOTE] Request for Waiver of Make a Release requirement for Incubator graduation On Tue, Nov 10, 2009 at 10:17 AM, Greg Stein wrote: Hello IPMC, The Subversion podling would like a waiver of the requirement to make a release before graduation. As we understand this requirement, it is present in order to demonstrate to the podling how releases are made at the ASF. Packaging, licensing, signing, placement into the distrubtion/mirror system, announcements, among others[1]. We believe that the Subversion community already has a deep understanding of the Apache release model, based on the following qualifications of several of its committers/mentors: Should we hold this vote to actually graduation time ? Would it be better to spend some of these debating energy to actually setup the Subversion podling into the Apache infrastructure, as currently I see no mailing lists, svn code import, etc... create the proper Apache user accounts for the several new committers, etc and maybe still give a chance to add new contributors... before worrying about this... Agreed. Starting the ball rolling by requesting a bunch of waivers is personally off-putting and bureaucratic. Something I'd like to see less off in the Incubator. /me shrugs Releases are the topic of the day. I wanted to get that whole discussion behind us, and move onto something constructive. I understand the rationale, but as others point out the request feels premature. IMO this won't put anything to rest, as people who insist on a release as an exit requirement will vote -1 twice now instead of once (for the graduation vote). I support the needs you have outlined for the subversion project in regards to domain names, etc. *because* the mentors are going to work to push this thru the IPMC in record time. If it turns out the mentors fail in this effort I will be personally disappointed in them and more reluctant to consider special cases for the Incubator in the future. This does mean the mentors also need to gather consensus within the IPMC as well as the Subversion project to agree on graduation concerns. The tactful approach is via early and open discussion, not formal preagreements. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Request for Waiver of Make a Release requirement for Incubator graduation
Consider this withdrawn for now. I'll resubmit when we think we're nearing time for graduation. Cheers, -g On Tue, Nov 10, 2009 at 13:17, Greg Stein gst...@gmail.com wrote: Hello IPMC, The Subversion podling would like a waiver of the requirement to make a release before graduation. As we understand this requirement, it is present in order to demonstrate to the podling how releases are made at the ASF. Packaging, licensing, signing, placement into the distrubtion/mirror system, announcements, among others[1]. We believe that the Subversion community already has a deep understanding of the Apache release model, based on the following qualifications of several of its committers/mentors: * Greg Stein has been a committer at Apache since before the Foundation was started. He has been involved in releases of httpd and APR, including time as Release Manager (RM) for APR. He helped to establish the APR TLP and the Commons TLP (prior incarnation; now defunct). Greg wrote the versioning guidelines for APR, which are also in use by the Subversion project. Through his 8+ years on the Board, he has read and reviewed reports from across the ASF about release, IP, and infrastructure issues. * Justin Erenkrantz has been a committer since 2001, contributing to httpd and APR, along with mentoring the stdcxx project when it was in the Incubator. He has been the RM for both httpd and APR. In fact, Justin wrote the initial guidelines for the release of httpd. Justin has been part of Infrastructure almost since its inception as a distinct group, which includes the provision of all the facilities to actually make and distribute ASF releases. Justin has spent many years on the Board, providing further insight to releases across the Foundation. * Sander Striker has been a committer since 2001, contributing to APR and then httpd. Sander acted as the RM for httpd releases, and also held a stint as the VP for httpd. Add in his time spent with Infrastructure and the Board, and he's been observing ASF releases for many years. * Garrett Rooney has been a committer since 2004, contributing and making releases of APR, and committing to httpd. He was also the VP of APR for several years, and has mentored two Incubating projects. * Daniel Rall has been a committer since 2001, contributing to many projects: Turbine, Fulcrum, Torque, and numerous Jakarta Commons projects. He established the community around XML-RPC, brought it through the Incubator, and maintained it for several years within the XML Project. He also participated in some of the bootstrapping around the Velocity and Maven projects, and participated on the Infra team. The Subversion community's belief is that we have ample experience to guide us in making a release, when that time is arrives. There will certainly be variances (e.g. mirroring) from our current established procedures[2], but some simple fine-tuning should resolve that. The bulk of the existing release process already meets and exceeds that a typical Apache release. Niclas Hedman pointed out that the Subversion community has produced 32 releases over the past four years, which hopefully indicates a smooth, understood, and functional release process. Cheers, -g [1] one particular item is using a release as a gating/focal point for legal review, but we feel that can be performed as an action separate/distinct from performing a release [2] http://subversion.tigris.org/release-process.html - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
