From Fedora Project Wiki
(Create initial WIP draft of the change proposal.)
 
(Enhancements)
Line 1: Line 1:
{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.<br/> '''Copy the source to a ''new page'' before making changes!  DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.'''}}
= Rubygem Cucumber 7.1.0 =
 
{{admon/tip | Guidance | For details on how to fill out this form, see the [https://docs.fedoraproject.org/en-US/program_management/changes_guide/ documentation].}}
 
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
 
= Rubygem Cucumber 7.0.0 =


== Summary ==
== Summary ==
Rubygem-cucumber 7.0.0 is the latest version of the popular integration BDD test suite for Ruby.
Rubygem-cucumber 7.1.0 is the latest version of the popular integration BDD test suite for Ruby.


== Owner ==
== Owner ==
<!--
For change proposals to qualify as self-contained, owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages.
This should link to your home wiki page so we know who you are.
-->
* Name: [[User:Jackorp1 | Jaroslav Prokop]], [[User:pvalena| Pavel Valena]]
* Name: [[User:Jackorp1 | Jaroslav Prokop]], [[User:pvalena| Pavel Valena]]
<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
* Email: jprokop@redhat.com, pvalena@redhat.com
* Email: jprokop@redhat.com, pvalena@redhat.com
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
-->


== Current status ==
== Current status ==
Line 30: Line 15:
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete-->
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete-->


<!-- Select proper category, default is Self Contained Change -->
[[Category:SelfContainedChange]]
[[Category:SelfContainedChange]]
<!-- [[Category:SystemWideChange]] -->


* Targeted release: [[Releases/36 | Fedora Linux 36 ]]  
* Targeted release: [[Releases/36 | Fedora Linux 36 ]]  
* Last updated: <!-- this is an automatic macro — you don't need to change this line -->  {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}  
* Last updated: {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}  
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page  
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page  
Bugzilla state meanings:
Bugzilla state meanings:
Line 47: Line 30:


== Detailed Description ==
== Detailed Description ==
Fedora is currently lagging behind on the Ruby cucumber test suite and as a result on new features and bug fixes. Therefore the rubygem-cucumber library stack will be updated to version 7.0.0, ensuring that Fedora has the newest Ruby cucumber test suite available.   
Fedora is currently lagging behind on the Ruby cucumber test suite and as a result on new features and bug fixes. Therefore the rubygem-cucumber library stack will be updated to version 7.1.0, ensuring that Fedora has the newest Ruby cucumber test suite available.   


== Benefit to Fedora ==
== Benefit to Fedora ==
This update will bring Rule and Rule tags support into Fedora as well as other improvements like bug fixes and features in the dependencies that are part of the Cucumber project.
This update will bring Rule and Rule tags, new hooks, and better plugin support into Fedora as well as other improvements like bug fixes and features in the dependencies that are part of the Cucumber project.


== Scope ==
== Scope ==
* Proposal owners:
* Proposal owners:
   * rubygem-cucumber and its dependencies have to be updated.
   * rubygem-cucumber and its dependencies will be updated.
  * Build rubygem-cucumber update and dependencies in sidetag.
   * Rebuild packages that depend on rubygem-cucumber and fix any that begin to fail as a result. <!-- not sure if there will be any failures, TODO: maybe delete? -->
   * Rebuild packages that depend on rubygem-cucumber and fix any that begin to fail as a result. <!-- not sure if there will be any failures, TODO: maybe delete? -->


Line 97: Line 81:


2.
2.
Find a project that uses Cucumber features with Ruby test implementation, and in it run:
Find a project that uses rubygem-cucumber 7.1.0 test implementation, and in that project run:
{{code}}
{{code}}
cucumber
cucumber
Line 108: Line 92:


== User Experience ==
== User Experience ==
* New version 7.0.0 available
* New version 7.1.0 available


== Dependencies ==
== Dependencies ==
* There are several packages, which depend on rubygem-cucumber test suite.
* There are several packages, which depend on the rubygem-cucumber test suite.
   * These need to be surely updated:
   * These need to be surely updated:
         TODO
         TODO
* Following gems don't support rubygem-cucumber 7.0.0 right now and would be broken by the update:
* Following gems don't support rubygem-cucumber 7.1.0 right now and would be broken by the update:
   * (none)
   * (none)


Line 121: Line 105:


* Contingency Plan
* Contingency Plan
   * Contingency mechanism: None needed. rubygem-cucumber itself won't be updated until all its dependencies are in Rawhide. After that, it will be a simple matter of updating the core packages (and their dependencies).
   * Contingency mechanism: None needed. rubygem-cucumber with its dependencies will be built in side-tag and merged after successful updates.
* Contingency deadline: N/A (not a System Wide Change)
* Contingency deadline: N/A (not a System Wide Change)
* Blocks release? No
* Blocks release? No
Line 128: Line 112:


== Documentation ==
== Documentation ==
<!-- TODO link my nice dep graph -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)  
N/A (not a System Wide Change)  
Line 139: Line 121:
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.  
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.  
-->
-->
Changelog: https://github.com/cucumber/cucumber-ruby/blob/v7.0.0/CHANGELOG.md
Users can use 'dnf install rubygem-cucumber' to install rubygem-cucumber.

Revision as of 10:33, 18 October 2021

Rubygem Cucumber 7.1.0

Summary

Rubygem-cucumber 7.1.0 is the latest version of the popular integration BDD test suite for Ruby.

Owner

Current status

  • Targeted release: Fedora Linux 36
  • Last updated: 2021-10-18
  • FESCo issue: <will be assigned by the Wrangler>
  • Tracker bug: <will be assigned by the Wrangler>
  • Release notes tracker: <will be assigned by the Wrangler>

Detailed Description

Fedora is currently lagging behind on the Ruby cucumber test suite and as a result on new features and bug fixes. Therefore the rubygem-cucumber library stack will be updated to version 7.1.0, ensuring that Fedora has the newest Ruby cucumber test suite available.

Benefit to Fedora

This update will bring Rule and Rule tags, new hooks, and better plugin support into Fedora as well as other improvements like bug fixes and features in the dependencies that are part of the Cucumber project.

Scope

  • Proposal owners:
 * rubygem-cucumber and its dependencies will be updated.
 * Build rubygem-cucumber update and dependencies in sidetag.
 * Rebuild packages that depend on rubygem-cucumber and fix any that begin to fail as a result. 
  • Trademark approval: N/A (not needed for this Change)
  • Alignment with Objectives:

Upgrade/compatibility impact

Upon upgrade it should still work for all users. Only exception being HTML output formatter which is currently not planned on being shipped.


How To Test

No special hardware is needed. 1. Prepare: To test using DNF, simply run {{{1}}} dnf install rubygem-cucumber Changes/rubygem-cucumber 7.0.0/code

2. Find a project that uses rubygem-cucumber 7.1.0 test implementation, and in that project run: {{{1}}} cucumber Changes/rubygem-cucumber 7.0.0/code

3. All tests should proceed as they do in upstream without cucumber crashing.


User Experience

  • New version 7.1.0 available

Dependencies

  • There are several packages, which depend on the rubygem-cucumber test suite.
 * These need to be surely updated:
       TODO
  • Following gems don't support rubygem-cucumber 7.1.0 right now and would be broken by the update:
 * (none)


Contingency Plan

  • Contingency Plan
 * Contingency mechanism: None needed. rubygem-cucumber with its dependencies will be built in side-tag and merged after successful updates.
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? No
  • Blocks product? No


Documentation

N/A (not a System Wide Change)

Release Notes

Users can use 'dnf install rubygem-cucumber' to install rubygem-cucumber.