# Is there a timeline or process for tagging releases?

**URL:** <https://discourse.slimframework.com/t/is-there-a-timeline-or-process-for-tagging-releases/5414>\
**Category:** Questions\
**Created:** [October 26, 2022, 10:22am UTC](https://discourse.slimframework.com/t/is-there-a-timeline-or-process-for-tagging-releases/5414 "2022-10-26T10:22:15Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![IMSoP](https://avatars.discourse-cdn.com/v4/letter/i/c6cbf5/32.png) [@IMSoP](https://discourse.slimframework.com/u/IMSoP)\
**Post date:** [October 26, 2022, 10:22am UTC](https://discourse.slimframework.com/t/is-there-a-timeline-or-process-for-tagging-releases/5414/1 "2022-10-26T10:22:15Z")

</div>

Hi lovely Slim people!

Thanks for this project, it’s a real treasure.

I’ve noticed that it’s been a while since the last release, both on the main framework and some of the other packages under the slimphp Github Organization. I wonder if there’s a process for when these will get tagged, or if it’s just a case of somebody with permission having the time to press the right buttons?

Specifically, I raised a bug in January against Slim-Psr7, and somebody kindly contributed a fix in March, but the last release of that package was over a year ago. Looking around, there seem to be similar small fixes unreleased on Slim-Csrf, Slim-Http and Slim-Skeleton as well as on the main Slim repo that would be good to see tagged.

Thanks again,  
Rowan Tommins  
[IMSoP]

---

<div class="post-metadata">

**Author:** ![odan](https://avatars.discourse-cdn.com/v4/letter/o/9de053/32.png) [@odan](https://discourse.slimframework.com/u/odan)\
**Post date:** [October 28, 2022, 1:39pm UTC](https://discourse.slimframework.com/t/is-there-a-timeline-or-process-for-tagging-releases/5414/2 "2022-10-28T13:39:30Z")

</div>

Hi @IMSoP As far as I know there is no timeline for releases defined.

Can you please link to the issues you have mentioned?

---

<div class="post-metadata">

**Author:** ![IMSoP](https://avatars.discourse-cdn.com/v4/letter/i/c6cbf5/32.png) [@IMSoP](https://discourse.slimframework.com/u/IMSoP)\
**Post date:** [November 1, 2022, 5:16pm UTC](https://discourse.slimframework.com/t/is-there-a-timeline-or-process-for-tagging-releases/5414/3 "2022-11-01T17:16:01Z")

</div>

Hi @odan,

The specific bug I’m personally interested in is this one: [Stream incorrectly reports write-only pipe (STDOUT) as readable · Issue #215 · slimphp/Slim-Psr7 · GitHub](https://github.com/slimphp/Slim-Psr7/issues/215)

In general, you can see the unreleased changes by comparing each repo’s latest tag against its main branch:

- [Comparing 1.5...master · slimphp/Slim-Psr7 · GitHub](https://github.com/slimphp/Slim-Psr7/compare/1.5...master)
- [Comparing 1.2.0...master · slimphp/Slim-Http · GitHub](https://github.com/slimphp/Slim-Http/compare/1.2.0...master)
- [Comparing 1.2.1...1.x · slimphp/Slim-Csrf · GitHub](https://github.com/slimphp/Slim-Csrf/compare/1.2.1...1.x)
- [Comparing 4.4.0...master · slimphp/Slim-Skeleton · GitHub](https://github.com/slimphp/Slim-Skeleton/compare/4.4.0...master)

Thanks for replying,  
Rowan

---

<div class="post-metadata">

**Author:** ![akrabat](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.slimframework.com/akrabat/32/9_2.png) [@akrabat](https://discourse.slimframework.com/u/akrabat)\
**Post date:** [November 2, 2022, 2:58pm UTC](https://discourse.slimframework.com/t/is-there-a-timeline-or-process-for-tagging-releases/5414/4 "2022-11-02T14:58:19Z")

</div>

@IMSoP, I’ll see what I can do

---

<div class="post-metadata">

**Author:** ![akrabat](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.slimframework.com/akrabat/32/9_2.png) [@akrabat](https://discourse.slimframework.com/u/akrabat)\
**Post date:** [November 5, 2022, 7:44pm UTC](https://discourse.slimframework.com/t/is-there-a-timeline-or-process-for-tagging-releases/5414/6 "2022-11-05T19:44:59Z")

</div>

New releases;

- Slim-Psr7 1.6: [Release 1.6.0 · slimphp/Slim-Psr7 · GitHub](https://github.com/slimphp/Slim-Psr7/releases/tag/1.6.0)
- Slim-Http 1.3.0: [Release 1.3.0 · slimphp/Slim-Http · GitHub](https://github.com/slimphp/Slim-Http/releases/tag/1.3.0)
- Slim-Csrf: 1.3.0: [Release 1.3.0 · slimphp/Slim-Csrf · GitHub](https://github.com/slimphp/Slim-Csrf/releases/tag/1.3.0)
- Slim-Skeleton: 4.5.0 [Release 4.5.0 · slimphp/Slim-Skeleton · GitHub](https://github.com/slimphp/Slim-Skeleton/releases/tag/4.5.0)

---

<div class="post-metadata">

**Author:** ![IMSoP](https://avatars.discourse-cdn.com/v4/letter/i/c6cbf5/32.png) [@IMSoP](https://discourse.slimframework.com/u/IMSoP)\
**Post date:** [November 7, 2022, 9:37am UTC](https://discourse.slimframework.com/t/is-there-a-timeline-or-process-for-tagging-releases/5414/7 "2022-11-07T09:37:17Z")

</div>

@akrabat Fantastic, thank you very much!