Date
1 - 3 of 3
Can a TSC member announce the 0.2.3 release in janusgraph-users
|
Chris Hupman <chris...@...>
I may be reading into formality a bit too much with this, but historically releases the releases have been announced on behalf of the technical steering committee. The wording could simply have been based off the fact that the previous 2 release managers were TSC members, but it does seem appropriate for the TSC to make the announcements. I'm working on updating the release documentation right now and we have the same scenario of a committer as release manager in 0.3.1 so it seems like a good time to iron out this detail. Regards, Chris |
|
|
|
Florian Hockmann <f...@...>
I think it should be the release manager in general to make the announcement. I don't see a reason why only TSC members should be able to do that if a committer can perform the release itself. Am Dienstag, 4. Juni 2019 01:10:51 UTC+2 schrieb Chris Hupman:
|
|
|
|
Chris Hupman <chris...@...>
Announcement sent and I'll add it as a step to the releasing docs. Technically anyone can make an announce thread and the TSC ultimately decides who can add as a release manager. Since the docs weren't totally flushed out and there was a lack of precedent I mainly wanted to verify. Just to share, I did some extra searching and found the apache announcing policy. The only tasks that it specifically recommended be done by PMC/TSC members were 1. release manager, and 2. signing artifacts. Both of which I was trusted to do as the release manager. So if anything I was focusing on the wrong gray area. On Tuesday, June 4, 2019 at 4:43:23 AM UTC-7, Florian Hockmann wrote:
|
|
|