Hi,
> Yes, we should start recommending your approach.
I think the IPMC need to decide as a whole on that first. Perhaps call a vote?
> I am actually for this as normal course and instituting the “pTLP” as the new
> normal as it is actually makes the PPMC more like a TLP from the start.
And
Hi Myrle,
Yes, we should start recommending your approach. I am actually for this as
normal course and instituting the “pTLP” as the new normal as it is actually
makes the PPMC more like a TLP from the start.
Given our current interpretation of rules that An Official Apache Release
requires 3
Hey all,
I've only heard positive feedback on this proposal. It doesn't solve all
our problems, but it would provide a path around some of the bureaucracy.
Would the other mentors be willing to bring this suggestion to their
podlings? Especially the "young" ones who still need releases outside
Hey Justin,
On Wed, Feb 27, 2019 at 8:33 AM Justin Mclean
wrote:
> How do we make podling aware they can do this? Obvious people who follow
> this list may know, and we can ask mentors to pass it on to their podling
> lists, on document on the website and perhaps mention it in Dave’s welcome
>
I would consider it a mentor responsibility, just like any other advise on
the way towards graduation. There could be explicit mention in the maturity
assessment / checklist.
--
sent from mobile
On Tue, Feb 26, 2019, 11:33 PM Justin Mclean
wrote:
> Hi,
>
> > But my proposal to move towards
Hi,
> But my proposal to move towards offering early feedback on
> releases works with or without this change.
+1
How do we make podling aware they can do this? Obvious people who follow this
list may know, and we can ask mentors to pass it on to their podling lists, on
document on the
Dave,
On Tue, Feb 26, 2019 at 10:30 PM Dave Fisher wrote:
> The IPMC could consider some changes to the Incubator rules. (As proposed
> mostly by Roy on private lists.)
>
> Allow the VOTE thread to be only on the dev@ list with 0 or 1 mentor vote
> required. As long as the DISCLAIMER exists
+1
I think this proposal could help a lot with how feedback is perceived by
podlings!
On Mon, Feb 25, 2019 at 11:51 PM Myrle Krantz wrote:
> Some podlings want or need feedback on their releases before they are ready
> to make official Apache releases. They want to discuss releases that are
>
Hi,
> Allow the VOTE thread to be only on the dev@ list with 0 or 1 mentor vote
> required. As long as the DISCLAIMER exists then the pooling release is good.
>
> Once completed the podling sends the vote thread to general@ with [REVIEW]
> (or [DISCUSS]). This allows the IPMC to review and
The IPMC could consider some changes to the Incubator rules. (As proposed
mostly by Roy on private lists.)
Allow the VOTE thread to be only on the dev@ list with 0 or 1 mentor vote
required. As long as the DISCLAIMER exists then the pooling release is good.
Once completed the podling sends the
Hi,
Nice idea. JFYI - This already happens, just not in a formal way, as I often
get emails to check podlings releases before they bring them to the IPMC.
> I encourage reviewers to review a release candidate, and vote, as early as
> possible in the 72 hour voting period. I also encourage them
This change would be useful.
As a release manager of a podling, the most disheartening thing is latency. The
usual practice is a 72 hour PPMC release vote, followed by a 72 hour IPMC vote,
one of which will cross a weekend, so a negative vote on the last day of the
IPMC vote adds at least a
12 matches
Mail list logo
