first release candidate

[Yonik Seeley <yo...@apache.org>]

Hi Iggy devs,

As I said on Discord, congrats on reaching the point of your first ASF
release! That’s a big milestone.

I’ve started looking at the release candidate, and in the meantime had
a couple of questions:

- Is running Apache RAT still considered a best practice for
incubating projects? If so, has it been run for this release?

- Was there a public discussion around cutting the release? While not
technically required, it’s generally a good sign that development
decisions are happening in the open. It was a bit unexpected to see a
release candidate and [VOTE] show up without any prior context. (For
reference, here’s an example of Lucene’s recent release discussion:
https://lists.apache.org/thread/1g4ob0sfbdhdjwhxhr3r3fqt4bjj4czr )

Unrelated to the release:

- The website should probably also link to the Apache mailing lists?

- I noticed the “newsletter” signup on the website -- what does that
refer to? Something like that would typically need to be developed
collaboratively by the community and signed off by the PMC.

Thanks,
-Yonik

Re: first release candidate

[Yonik Seeley <ys...@gmail.com>]

On Sun, Apr 13, 2025 at 10:32 PM Kranti Parisa <kr...@apache.org> wrote:
[...]
> Release Discussion:
> ----
> We have been discussing on the Discord channel and initiated the Iggy
> community (PPMC) Voting thread before sending to IPMC.
> Seems other incubator projects are also operating this way, example
> https://lists.apache.org/list.html?dev@hertzbeat.apache.org

OK, good.  It was any public discussion I was looking for (I looked,
but didn't see it on the Discord channels)

> Going forward we can very well start a mailing list [DISCUSSION] thread for
> Iggy Dev community before the [VOTE]

Nothing needs to be formalized IMO - this is more about an open
development process.

> Currently this is what we've planned to follow:
> 1. Discuss on Discord channel. being a small and growing community, we've
> observed much active and faster collaboration on the channel.

I personally think that's fine, but opinions vary.  The ASF is
currently grappling with these
shifting developer preferences, esp around where decisions are made
and how to ensure they are archived forever.

> However for
> important topics we're encouraging people to use GitHub Discussions
> https://github.com/apache/iggy/discussions.
> 2. Initiate Iggy PPMC [VOTE] thread

Indeed.  At this point (if Iggy were a TLP), the VOTE for a release
*must* currently happen for legal reasons
on the mailing-lists (which a GitHub Discussion fulfills since it's
forwarded to the mailing lists.)

[...]
> Website:
> ----
> If you are referring to iggy.rs website, it's old and we will be
> redirecting it to iggy.apache.org in coming weeks.

Ah, thanks... didn't realize I wasn't on the ASF site.

-Yonik

Re: first release candidate

[Kranti Parisa <kr...@apache.org>]

Thanks Yonik, please find answers below.

Apache RAT:
----
No, we didn't use. I'm not very sure if that's used by latest incubator
projects. Need to research more, looks more for ant, mvn based builds?

Release Discussion:
----
We have been discussing on the Discord channel and initiated the Iggy
community (PPMC) Voting thread before sending to IPMC.
Seems other incubator projects are also operating this way, example
https://lists.apache.org/list.html?dev@hertzbeat.apache.org

Going forward we can very well start a mailing list [DISCUSSION] thread for
Iggy Dev community before the [VOTE]

Currently this is what we've planned to follow:
1. Discuss on Discord channel. being a small and growing community, we've
observed much active and faster collaboration on the channel. However for
important topics we're encouraging people to use GitHub Discussions
https://github.com/apache/iggy/discussions.
2. Initiate Iggy PPMC [VOTE] thread
3. Summarize [VOTE][RESULT] at Iggy PPMC level
4. If Iggy PPMC approves, send the [VOTE] request to IPMC
5. Summarize [VOTE][RESULT] at IPMC level
6. If IPMC approves, send [ANNOUNCE] about the Release to IPMC, Iggy PPMC
https://incubator.apache.org/guides/releasemanagement.html
This seems to be the general process followed by other Incubator projects.

Website:
----
If you are referring to iggy.rs website, it's old and we will be
redirecting it to iggy.apache.org in coming weeks.

We've a PR open for the contributor guide. And yes we'll be adding all the
mailing lists as well, that should be the way for people to subscribe to
get updates dev@ users@ maybe we should have news@ not sure if that
required. Any thoughts?
https://github.com/apache/iggy/pull/1687/files


Best,
Kranti



On Sun, Apr 13, 2025 at 6:05 PM Yonik Seeley <yo...@apache.org> wrote:

> Hi Iggy devs,
>
> As I said on Discord, congrats on reaching the point of your first ASF
> release! That’s a big milestone.
>
> I’ve started looking at the release candidate, and in the meantime had
> a couple of questions:
>
> - Is running Apache RAT still considered a best practice for
> incubating projects? If so, has it been run for this release?
>
> - Was there a public discussion around cutting the release? While not
> technically required, it’s generally a good sign that development
> decisions are happening in the open. It was a bit unexpected to see a
> release candidate and [VOTE] show up without any prior context. (For
> reference, here’s an example of Lucene’s recent release discussion:
> https://lists.apache.org/thread/1g4ob0sfbdhdjwhxhr3r3fqt4bjj4czr )
>
> Unrelated to the release:
>
> - The website should probably also link to the Apache mailing lists?
>
> - I noticed the “newsletter” signup on the website -- what does that
> refer to? Something like that would typically need to be developed
> collaboratively by the community and signed off by the PMC.
>
> Thanks,
> -Yonik
>