ruby-i18n / ruby-i18n/ruby-cldr
Releasing `ruby-cldr`
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 78
- Forks
- 18
- Avg merge
- 9d 8h
- Merged PRs (30d)
- 3
Description
Hello @camertron,
We've been working away at improving ruby-cldr and getting it to a point where it can be used with the latest version of CLDR (v41).
While we're not yet ready for a 1.0.0 release, I think it would be good to get a 0.6.0 release done.
What would the process be to do this? Who currently has the keys/permission to publish to RubyGems, and is it possible to have those transferred over to me? (I saw that you were the last to publish ruby-cldr to RubyGems)
Just kicking off the conversation now.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the issue discussion and the ruby-cldr repository's release process; no files or tests are named. Determine who can publish ruby-cldr to RubyGems, whether the project is ready for a 0.6.0 release, and what permission transfer process applies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100