Re: Tags in the commitfest app: How to use them and what tags to add?
От | Jacob Champion |
---|---|
Тема | Re: Tags in the commitfest app: How to use them and what tags to add? |
Дата | |
Msg-id | CAOYmi+n8dcy+tQdQHL=qOHhemyZtPDF3gGvBN1Anu2kQoDFYpA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Tags in the commitfest app: How to use them and what tags to add? (Jelte Fennema-Nio <me@jeltef.nl>) |
Список | pgsql-hackers |
On Tue, Jul 1, 2025 at 12:33 AM Jelte Fennema-Nio <me@jeltef.nl> wrote: > I think maybe we > should show the search/filter bar by default, because I keep > forgetting it exists and I continue to use regular Ctrl+F instead. Hmm, I think I agree. > I quite dislike the current topic system. Me too. :) > Unsurprisingly, people don't always update this version throughout the > years. So a label that was meant one way, might suddenly start to mean > something completely else. > > Then there's "stable", which afaict is a way of saying something needs > to be backported? But it's currently unknown yet how far exactly. I view it as "all applicable stable branches", yes. > So a PROPOSAL to clarify the version column: > 1. Rename "stable" to "backport" > 2. Add some info to the help page, and the label > 3. Introduce a "current" and a "next" version, those might still > reflect an outdated state, but at least they don't start to mean > different things when they are not being updated. During beta, what's "current" and what's "next"? What's the motivation to put something in "next" rather than just leaving it blank? --Jacob
В списке pgsql-hackers по дате отправления: