[VOTE] Release Tobago 4.5.3
Hello, We would like to release * Tobago 4.5.3 The demos on Tobago VM [1] are up to date. Major changes since last release are: * Tobago 4.5.3 o Bugfix For a detail list please consult the release notes in Jira for * Tobago 4.5.3 [2]. The version is available at the staging repository (Nexus) at: * Tobago 4.5.3 o Staging Repo 1183 [3] o Source Artefact [4] o sha-256 e1a880b85710f83fd72d7c6b8edaadcd1921a2d057139f4bcf2eece36d216e0b Please vote now! (The vote is open for 72h.) [ ] +1 [ ] +0 [ ] -1 Regards, Udo [1] http://tobago-vm.apache.org/ [2] https://issues.apache.org/jira/issues/?jql=project%20%3D%20TOBAGO%20AND%20fixVersion%20%3D%204.5.3 [3] https://repository.apache.org/content/repositories/orgapachemyfaces-1183/ [4] https://repository.apache.org/content/repositories/orgapachemyfaces-1183/org/apache/myfaces/tobago/tobago/4.5.3/tobago-4.5.3-source-release.zip
[GitHub] [myfaces-tobago] lofwyr14 opened a new pull request #568: docs (tobago-vm): prepare vote for next release
lofwyr14 opened a new pull request #568: URL: https://github.com/apache/myfaces-tobago/pull/568 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [myfaces-tobago] lofwyr14 merged pull request #568: docs (tobago-vm): prepare vote for next release
lofwyr14 merged pull request #568: URL: https://github.com/apache/myfaces-tobago/pull/568 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [myfaces-tobago] lofwyr14 merged pull request #566: Prepare release
lofwyr14 merged pull request #566: URL: https://github.com/apache/myfaces-tobago/pull/566 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [myfaces-tobago] lofwyr14 closed pull request #567: Prepare release
lofwyr14 closed pull request #567: URL: https://github.com/apache/myfaces-tobago/pull/567 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [myfaces-tobago] lofwyr14 opened a new pull request #567: Prepare release
lofwyr14 opened a new pull request #567: URL: https://github.com/apache/myfaces-tobago/pull/567 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [myfaces-tobago] lofwyr14 opened a new pull request #566: Prepare release
lofwyr14 opened a new pull request #566: URL: https://github.com/apache/myfaces-tobago/pull/566 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [myfaces-tobago] lofwyr14 merged pull request #565: Demo: Menu Entry
lofwyr14 merged pull request #565: URL: https://github.com/apache/myfaces-tobago/pull/565 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [myfaces-tobago] lofwyr14 opened a new pull request #565: Demo: Menu Entry
lofwyr14 opened a new pull request #565: URL: https://github.com/apache/myfaces-tobago/pull/565 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [myfaces-tobago] henningn commented on a change in pull request #344: docs: add contributing info and code of conduct
henningn commented on a change in pull request #344: URL: https://github.com/apache/myfaces-tobago/pull/344#discussion_r583597787 ## File path: CONTRIBUTING.md ## @@ -0,0 +1,70 @@ +# (WIP) Contributing Info + +## Semantic Commit Messages + +Inspired by [Git Commit Msg][git-commit-msg], [Angular Commit Message Format][angular-commit-message-format] and [Conventional Commits][conventional-commits] + + +### Commit Message Format + +Each commit message consists of a **header**, a **body** and a **footer**. The header has a special +format that includes a **type**, a **scope**, and a **subject**: + +```html +(): + + + + +``` + +> Any line of the commit message cannot be longer 100 characters! +This allows the message to be easier to read on GitHub as well as in various Git tools. + +# Type + +Must be one of the following: + +* **feat**: A new feature +* **fix**: A bug fix +* **docs**: Documentation only changes +* **style**: Changes that do not affect the meaning of the code (white-space, formatting, missing + semi-colons, etc) +* **refactor**: A code change that neither fixes a bug nor adds a feature +* **perf**: A code change that improves performance +* **test**: Adding missing tests +* **chore**: Changes to the auxiliary tools such as release scripts +* **build**: Changes to the dependencies, devDependencies, or build tooling +* **ci**: Changes to our Continuous Integration configuration + +# Scope + +The scope could be anything that helps specify the scope (or feature) that is changing. + +Examples +- fix(select): +- docs(menu): + +# Subject + +The subject contains a succinct description of the change: + +* use the imperative, present tense: "change" not "changed" nor "changes" +* don't capitalize first letter +* no period (.) at the end + +# Body + +Just as in the **subject**, use the imperative, present tense: "change" not "changed" nor "changes". +The body should include the motivation for the change and contrast this with previous behavior. + +# Footer + +The footer should contain any information about **Breaking Changes** and is also the place to +reference Jira issues that this commit **Closes**, **Fixes**, or **Relates to**. Review comment: Do we need "Closes, Fixes, Relates to" for referencing an Issue? We could use "Issue: TOBAGO-1234" instead. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [myfaces-tobago] henningn commented on a change in pull request #344: docs: add contributing info and code of conduct
henningn commented on a change in pull request #344: URL: https://github.com/apache/myfaces-tobago/pull/344#discussion_r583597385 ## File path: CONTRIBUTING.md ## @@ -0,0 +1,70 @@ +# (WIP) Contributing Info + +## Semantic Commit Messages + +Inspired by [Git Commit Msg][git-commit-msg], [Angular Commit Message Format][angular-commit-message-format] and [Conventional Commits][conventional-commits] + + +### Commit Message Format + +Each commit message consists of a **header**, a **body** and a **footer**. The header has a special +format that includes a **type**, a **scope**, and a **subject**: + +```html +(): + + + + +``` + +> Any line of the commit message cannot be longer 100 characters! +This allows the message to be easier to read on GitHub as well as in various Git tools. + +# Type + +Must be one of the following: + +* **feat**: A new feature +* **fix**: A bug fix +* **docs**: Documentation only changes +* **style**: Changes that do not affect the meaning of the code (white-space, formatting, missing + semi-colons, etc) +* **refactor**: A code change that neither fixes a bug nor adds a feature +* **perf**: A code change that improves performance +* **test**: Adding missing tests +* **chore**: Changes to the auxiliary tools such as release scripts +* **build**: Changes to the dependencies, devDependencies, or build tooling +* **ci**: Changes to our Continuous Integration configuration + +# Scope + +The scope could be anything that helps specify the scope (or feature) that is changing. Review comment: Should the scope be optional? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [myfaces-tobago] henningn commented on a change in pull request #344: docs: add contributing info and code of conduct
henningn commented on a change in pull request #344: URL: https://github.com/apache/myfaces-tobago/pull/344#discussion_r583597218 ## File path: CONTRIBUTING.md ## @@ -0,0 +1,70 @@ +# (WIP) Contributing Info + +## Semantic Commit Messages + +Inspired by [Git Commit Msg][git-commit-msg], [Angular Commit Message Format][angular-commit-message-format] and [Conventional Commits][conventional-commits] + + +### Commit Message Format + +Each commit message consists of a **header**, a **body** and a **footer**. The header has a special +format that includes a **type**, a **scope**, and a **subject**: + +```html +(): + + + + +``` + +> Any line of the commit message cannot be longer 100 characters! +This allows the message to be easier to read on GitHub as well as in various Git tools. + +# Type + +Must be one of the following: + +* **feat**: A new feature +* **fix**: A bug fix +* **docs**: Documentation only changes +* **style**: Changes that do not affect the meaning of the code (white-space, formatting, missing + semi-colons, etc) +* **refactor**: A code change that neither fixes a bug nor adds a feature +* **perf**: A code change that improves performance +* **test**: Adding missing tests +* **chore**: Changes to the auxiliary tools such as release scripts +* **build**: Changes to the dependencies, devDependencies, or build tooling +* **ci**: Changes to our Continuous Integration configuration Review comment: Do we need so many different type types? "perf" seems to be a subtype of "refactor". "build" and "ci" may be a subtype of "chore". So I suggest to remove those subtypes. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: svn commit: r1886879 - /comdev/projects.apache.org/trunk/data/projects.xml
Should be fixed now Thanks On Wed, Feb 24, 2021 at 1:39 PM sebb AT ASF wrote: > The DOAP is still missing, so has been commented out. > > -- Forwarded message - > From: > Date: Wed, 24 Feb 2021 at 12:37 > Subject: svn commit: r1886879 - > /comdev/projects.apache.org/trunk/data/projects.xml > To: > > > Author: sebb > Date: Wed Feb 24 12:37:36 2021 > New Revision: 1886879 > > URL: http://svn.apache.org/viewvc?rev=1886879=rev > Log: > MyFaces DOAP AWOL > > Modified: > comdev/projects.apache.org/trunk/data/projects.xml > > Modified: comdev/projects.apache.org/trunk/data/projects.xml > URL: > http://svn.apache.org/viewvc/comdev/projects.apache.org/trunk/data/projects.xml?rev=1886879=1886878=1886879=diff > > == > --- comdev/projects.apache.org/trunk/data/projects.xml (original) > +++ comdev/projects.apache.org/trunk/data/projects.xml Wed Feb 24 > 12:37:36 2021 > @@ -240,7 +240,7 @@ >http://svn.apache.org/repos/asf/mina/metadata/vysper.rdf > > > https://gitbox.apache.org/repos/asf?p=incubator-mxnet.git;a=blob_plain;f=doap.rdf;hb=HEAD > > > https://gitbox.apache.org/repos/asf?p=attic-mrunit.git;f=doap_mrunit.rdf;a=blob_plain;hb=HEAD > > - http://myfaces.apache.org/doap_MyFaces.rdf > + > > https://gitbox.apache.org/repos/asf?p=myfaces-tobago.git;a=blob_plain;f=doap.rdf;hb=HEAD > >http://nutch.apache.org/doap.rdf >https://ofbiz.apache.org/doap_OFBiz.rdf >
[GitHub] [myfaces] bohmber merged pull request #179: chore(asf): add doap file
bohmber merged pull request #179: URL: https://github.com/apache/myfaces/pull/179 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [myfaces] bohmber opened a new pull request #179: chore(asf): add doap file
bohmber opened a new pull request #179: URL: https://github.com/apache/myfaces/pull/179 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
