Re: When's Trinidad/ADFFaces graduation?
Hi Mike, see some comments inline. On 2/4/07, Mike Kienenberger [EMAIL PROTECTED] wrote: Speaking of incubator issues, what's holding up graduation of Trinidad at this point? From what I've seen, the community is active and understands the Apache way. I agree The status page appears to have checked off all of the outstanding tasks. The only relevent thing in the last board report (which is missing from the status page, by the way) was cleanup of notices and licenses for compliance with the ASF and there's no indication that any further incubating tasks are pending. http://wiki.apache.org/incubator/December2006 I overhauled the source files to met compliance w/ the ASF during the last month. all JARs now also contain the NOTICE.TXT and LICENSE.TXT As far as I know, the only thing that might be holding up graduation is a dry-run through a release, and that doesn't have to wait until there's a real release ready. Martin van den Bemt (our mentor) and me are working on that. I am fighting with a maven profile (see my next email) I'd be +1 on accepting Trinidad under MyFaces at this point. I am definitely +1 on that as well. (binding like yours from MyFaces PMC standpoint) How did you guys handle that with Cayenne ? Did you guys voted in your dev list on that?`Or just *asking* for graduation on the [EMAIL PROTECTED] list ? -Matthias -- Matthias Wessendorf http://tinyurl.com/fmywh further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
[release] adding a maven profile ?
Hello friends, Martin van den Bemt and I are working on the release of the plugins. I'd like to add a profile like the attached one (take from Tobago). With that profile we'll do the following. -Do the release and deploy it to the Incubator SNAPSHOT repository -Hold a vote on the bits and bytes on Trinidad DEV -Move the vote to the [EMAIL PROTECTED] list -do the release (means *moving* it to a non-snapshot incubator repo) The maven release-plugin changes those -SNAPSHOT things, so the Incubator PMC hasn't to vote on a snapshot (only deployed to a snapshot repo, easy to *redeloy*). So the *vote candidate* and the *real* release artifacts would be the same. (that was one side note on a formal thread at the general_incubator list, to not vote on a SNAPSHOT) When putting the profile to the plugins release branch, I'd like to start to change the versions as discussed in my past email (also a side note on a incubator thread, to have proper versions like 1.0.0-incubating instead of incubator-m1). Feedback welcome! -Matthias --- the profile: profile idrelease/id !-- NOTE: To use you need to enable this profile and pass in the passphrase: mvn -Prelease -Dpassphrase=thephrase -- build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-gpg-plugin/artifactId executions execution idsign-artifacts/id phaseverify/phase goals goalsign/goal /goals /execution /executions /plugin plugin artifactIdmaven-source-plugin/artifactId version2.0.1/version executions execution idattach-sources/id goals goaljar/goal /goals /execution /executions /plugin plugin artifactIdmaven-javadoc-plugin/artifactId version2.1/version executions execution idattach-javadocs/id goals goaljar/goal /goals /execution /executions /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-scm-plugin/artifactId executions execution phasevalidate/phase idgetting-scm.revision/id goalsgoalupdate/goal/goals /execution /executions /plugin /plugins /build /profile
Re: [release] adding a maven profile ?
Hello Matthias, please look at this pom, too http://svn.apache.org/viewvc/maven/pom/tags/maven-parent-5/pom.xml?revision=502493view=markup you can configure the deploy-plugin to deploy the artifacts to a diffenent location. Regards Bernd Matthias Wessendorf wrote: Hello friends, Martin van den Bemt and I are working on the release of the plugins. I'd like to add a profile like the attached one (take from Tobago). With that profile we'll do the following. -Do the release and deploy it to the Incubator SNAPSHOT repository -Hold a vote on the bits and bytes on Trinidad DEV -Move the vote to the [EMAIL PROTECTED] list -do the release (means *moving* it to a non-snapshot incubator repo) The maven release-plugin changes those -SNAPSHOT things, so the Incubator PMC hasn't to vote on a snapshot (only deployed to a snapshot repo, easy to *redeloy*). So the *vote candidate* and the *real* release artifacts would be the same. (that was one side note on a formal thread at the general_incubator list, to not vote on a SNAPSHOT) When putting the profile to the plugins release branch, I'd like to start to change the versions as discussed in my past email (also a side note on a incubator thread, to have proper versions like 1.0.0-incubating instead of incubator-m1). Feedback welcome! -Matthias --- the profile: profile idrelease/id !-- NOTE: To use you need to enable this profile and pass in the passphrase: mvn -Prelease -Dpassphrase=thephrase -- build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-gpg-plugin/artifactId executions execution idsign-artifacts/id phaseverify/phase goals goalsign/goal /goals /execution /executions /plugin plugin artifactIdmaven-source-plugin/artifactId version2.0.1/version executions execution idattach-sources/id goals goaljar/goal /goals /execution /executions /plugin plugin artifactIdmaven-javadoc-plugin/artifactId version2.1/version executions execution idattach-javadocs/id goals goaljar/goal /goals /execution /executions /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-scm-plugin/artifactId executions execution phasevalidate/phase idgetting-scm.revision/id goalsgoalupdate/goal/goals /execution /executions /plugin /plugins /build /profile
Re: [release] adding a maven profile ?
Hey Börnd, you are talking about those *staging* locations, right`? -M On 2/4/07, Bernd Bohmann [EMAIL PROTECTED] wrote: Hello Matthias, please look at this pom, too http://svn.apache.org/viewvc/maven/pom/tags/maven-parent-5/pom.xml?revision=502493view=markup you can configure the deploy-plugin to deploy the artifacts to a diffenent location. Regards Bernd Matthias Wessendorf wrote: Hello friends, Martin van den Bemt and I are working on the release of the plugins. I'd like to add a profile like the attached one (take from Tobago). With that profile we'll do the following. -Do the release and deploy it to the Incubator SNAPSHOT repository -Hold a vote on the bits and bytes on Trinidad DEV -Move the vote to the [EMAIL PROTECTED] list -do the release (means *moving* it to a non-snapshot incubator repo) The maven release-plugin changes those -SNAPSHOT things, so the Incubator PMC hasn't to vote on a snapshot (only deployed to a snapshot repo, easy to *redeloy*). So the *vote candidate* and the *real* release artifacts would be the same. (that was one side note on a formal thread at the general_incubator list, to not vote on a SNAPSHOT) When putting the profile to the plugins release branch, I'd like to start to change the versions as discussed in my past email (also a side note on a incubator thread, to have proper versions like 1.0.0-incubating instead of incubator-m1). Feedback welcome! -Matthias --- the profile: profile idrelease/id !-- NOTE: To use you need to enable this profile and pass in the passphrase: mvn -Prelease -Dpassphrase=thephrase -- build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-gpg-plugin/artifactId executions execution idsign-artifacts/id phaseverify/phase goals goalsign/goal /goals /execution /executions /plugin plugin artifactIdmaven-source-plugin/artifactId version2.0.1/version executions execution idattach-sources/id goals goaljar/goal /goals /execution /executions /plugin plugin artifactIdmaven-javadoc-plugin/artifactId version2.1/version executions execution idattach-javadocs/id goals goaljar/goal /goals /execution /executions /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-scm-plugin/artifactId executions execution phasevalidate/phase idgetting-scm.revision/id goalsgoalupdate/goal/goals /execution /executions /plugin /plugins /build /profile -- Matthias Wessendorf http://tinyurl.com/fmywh further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
Re: [release] adding a maven profile ?
yes watching handball worldcup :-) Matthias Wessendorf wrote: Hey Börnd, you are talking about those *staging* locations, right`? -M On 2/4/07, Bernd Bohmann [EMAIL PROTECTED] wrote: Hello Matthias, please look at this pom, too http://svn.apache.org/viewvc/maven/pom/tags/maven-parent-5/pom.xml?revision=502493view=markup you can configure the deploy-plugin to deploy the artifacts to a diffenent location. Regards Bernd Matthias Wessendorf wrote: Hello friends, Martin van den Bemt and I are working on the release of the plugins. I'd like to add a profile like the attached one (take from Tobago). With that profile we'll do the following. -Do the release and deploy it to the Incubator SNAPSHOT repository -Hold a vote on the bits and bytes on Trinidad DEV -Move the vote to the [EMAIL PROTECTED] list -do the release (means *moving* it to a non-snapshot incubator repo) The maven release-plugin changes those -SNAPSHOT things, so the Incubator PMC hasn't to vote on a snapshot (only deployed to a snapshot repo, easy to *redeloy*). So the *vote candidate* and the *real* release artifacts would be the same. (that was one side note on a formal thread at the general_incubator list, to not vote on a SNAPSHOT) When putting the profile to the plugins release branch, I'd like to start to change the versions as discussed in my past email (also a side note on a incubator thread, to have proper versions like 1.0.0-incubating instead of incubator-m1). Feedback welcome! -Matthias --- the profile: profile idrelease/id !-- NOTE: To use you need to enable this profile and pass in the passphrase: mvn -Prelease -Dpassphrase=thephrase -- build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-gpg-plugin/artifactId executions execution idsign-artifacts/id phaseverify/phase goals goalsign/goal /goals /execution /executions /plugin plugin artifactIdmaven-source-plugin/artifactId version2.0.1/version executions execution idattach-sources/id goals goaljar/goal /goals /execution /executions /plugin plugin artifactIdmaven-javadoc-plugin/artifactId version2.1/version executions execution idattach-javadocs/id goals goaljar/goal /goals /execution /executions /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-scm-plugin/artifactId executions execution phasevalidate/phase idgetting-scm.revision/id goalsgoalupdate/goal/goals /execution /executions /plugin /plugins /build /profile
Re: [release] adding a maven profile ?
yes ok, I was having issues when trying to upload the artifacts to my Apache $HOME, perhaps the VPN... ? But works also with *local* dirs and I can do the upload on my own. watching handball worldcup :-) same here. Germany !!! Matthias Wessendorf wrote: Hey Börnd, you are talking about those *staging* locations, right`? -M On 2/4/07, Bernd Bohmann [EMAIL PROTECTED] wrote: Hello Matthias, please look at this pom, too http://svn.apache.org/viewvc/maven/pom/tags/maven-parent-5/pom.xml?revision=502493view=markup you can configure the deploy-plugin to deploy the artifacts to a diffenent location. Regards Bernd Matthias Wessendorf wrote: Hello friends, Martin van den Bemt and I are working on the release of the plugins. I'd like to add a profile like the attached one (take from Tobago). With that profile we'll do the following. -Do the release and deploy it to the Incubator SNAPSHOT repository -Hold a vote on the bits and bytes on Trinidad DEV -Move the vote to the [EMAIL PROTECTED] list -do the release (means *moving* it to a non-snapshot incubator repo) The maven release-plugin changes those -SNAPSHOT things, so the Incubator PMC hasn't to vote on a snapshot (only deployed to a snapshot repo, easy to *redeloy*). So the *vote candidate* and the *real* release artifacts would be the same. (that was one side note on a formal thread at the general_incubator list, to not vote on a SNAPSHOT) When putting the profile to the plugins release branch, I'd like to start to change the versions as discussed in my past email (also a side note on a incubator thread, to have proper versions like 1.0.0-incubating instead of incubator-m1). Feedback welcome! -Matthias --- the profile: profile idrelease/id !-- NOTE: To use you need to enable this profile and pass in the passphrase: mvn -Prelease -Dpassphrase=thephrase -- build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-gpg-plugin/artifactId executions execution idsign-artifacts/id phaseverify/phase goals goalsign/goal /goals /execution /executions /plugin plugin artifactIdmaven-source-plugin/artifactId version2.0.1/version executions execution idattach-sources/id goals goaljar/goal /goals /execution /executions /plugin plugin artifactIdmaven-javadoc-plugin/artifactId version2.1/version executions execution idattach-javadocs/id goals goaljar/goal /goals /execution /executions /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-scm-plugin/artifactId executions execution phasevalidate/phase idgetting-scm.revision/id goalsgoalupdate/goal/goals /execution /executions /plugin /plugins /build /profile -- Matthias Wessendorf http://tinyurl.com/fmywh further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
Re: versioning
Sure, d'accord - just like the Tomcat folks do it, it doesn't make sense to keep the product versions fully at the spec or API versions. We should do the same for MyFaces and Tomahawk, by the way. regards, Martin On 2/4/07, Matthias Wessendorf [EMAIL PROTECTED] wrote: resent, because went to PMC list. On 2/3/07, Matthias Wessendorf [EMAIL PROTECTED] wrote: hi guys, currently our stuff has no real version number; only M1, which is almost nothing. I think we should name the current Trinidad stuff 1.0.0 and put the m1 (or incubator or incubating) to it, because of being incubator (for plugins and core). So something like: versionincubator-m1-SNAPSHOT/version would be: version1.0.0-incubating-SNAPSHOT/version The incubating I saw, when looking at OpenJPA. (of course w/o SNAPSHOT, after we do a release) For the JSF 1.2 branch I suggest to use the version 2.0 I think it doesn't make sense to follow the JSF version system in the version system of us. So, according to some blog entries, the next version for JSF (targeted for Java EE 6), will be called JSF 6. That would mean, if we stay tightly with their system we'd have a release or Trinidad 1.0 (mustn't it be 1.1 ??) Trinidad 1.2 Trinidad 6 which is really confusing (to me). So, to sum it up: -the current Trinidad stuff (based on JSF 1.1) will be 1.0.0 -the *future* stuff (based on JSF 1.2) will be the 2.0.0 stuff -In case of JSF 6, we simply have a 3.0.0. -using $version-incubating instead of $version-m1 Any comments ? -Matthias -- Matthias Wessendorf http://tinyurl.com/fmywh further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com -- Matthias Wessendorf http://tinyurl.com/fmywh further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
Re: When's Trinidad/ADFFaces graduation?
For graduation votes the following needs to happen : - Vote on this list for graduation - Vote on incubator general - The MyFaces PMC needs to vote to accept Trinidad (or the board if trinidad goes TLP) Before we start a vote however, I would still want to walk through this checklist http://incubator.apache.org/incubation/Incubation_Policy.html#Exiting+the+Incubator. Please don't start answering all things above yet, since it is something I want to figure out, since people on the incubator PMC would probably do the same and it's better that we hit the problem areas than when the vote on general happens. I will try to get the mail out to the dev in the coming week. Mvgr, Martin Matthias Wessendorf wrote: Hi Mike, see some comments inline. On 2/4/07, Mike Kienenberger [EMAIL PROTECTED] wrote: Speaking of incubator issues, what's holding up graduation of Trinidad at this point? From what I've seen, the community is active and understands the Apache way. I agree The status page appears to have checked off all of the outstanding tasks. The only relevent thing in the last board report (which is missing from the status page, by the way) was cleanup of notices and licenses for compliance with the ASF and there's no indication that any further incubating tasks are pending. http://wiki.apache.org/incubator/December2006 I overhauled the source files to met compliance w/ the ASF during the last month. all JARs now also contain the NOTICE.TXT and LICENSE.TXT As far as I know, the only thing that might be holding up graduation is a dry-run through a release, and that doesn't have to wait until there's a real release ready. Martin van den Bemt (our mentor) and me are working on that. I am fighting with a maven profile (see my next email) I'd be +1 on accepting Trinidad under MyFaces at this point. I am definitely +1 on that as well. (binding like yours from MyFaces PMC standpoint) How did you guys handle that with Cayenne ? Did you guys voted in your dev list on that?`Or just *asking* for graduation on the [EMAIL PROTECTED] list ? -Matthias
Re: When's Trinidad/ADFFaces graduation?
For Cayenne, it was as Martin posted. First we voted on the project dev list, then we asked for an incubator PMC vote on general, then we waited for the board to approve Cayenne as a TLP. On 2/4/07, Matthias Wessendorf [EMAIL PROTECTED] wrote: Hi Mike, see some comments inline. On 2/4/07, Mike Kienenberger [EMAIL PROTECTED] wrote: Speaking of incubator issues, what's holding up graduation of Trinidad at this point? From what I've seen, the community is active and understands the Apache way. I agree The status page appears to have checked off all of the outstanding tasks. The only relevent thing in the last board report (which is missing from the status page, by the way) was cleanup of notices and licenses for compliance with the ASF and there's no indication that any further incubating tasks are pending. http://wiki.apache.org/incubator/December2006 I overhauled the source files to met compliance w/ the ASF during the last month. all JARs now also contain the NOTICE.TXT and LICENSE.TXT As far as I know, the only thing that might be holding up graduation is a dry-run through a release, and that doesn't have to wait until there's a real release ready. Martin van den Bemt (our mentor) and me are working on that. I am fighting with a maven profile (see my next email) I'd be +1 on accepting Trinidad under MyFaces at this point. I am definitely +1 on that as well. (binding like yours from MyFaces PMC standpoint) How did you guys handle that with Cayenne ? Did you guys voted in your dev list on that?`Or just *asking* for graduation on the [EMAIL PROTECTED] list ? -Matthias -- Matthias Wessendorf http://tinyurl.com/fmywh further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
