[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [eclipse.org-planning-council] Managing opt-in/opt-out
- From: Nick Boldt <nboldt@xxxxxxxxxx>
- Date: Tue, 20 Aug 2019 16:59:05 -0400
- Delivered-to: email@example.com
Yes, that's what I was suggesting:
> We could also consider having a heavy-handed "miss M2 and you're out " policy for the annual June releases, and a "if you were in for June you can coast through the year without opting in again and again" policy for the other 3 releases, which aligns with the old annual simrel trains' opt-in process and gets around the apathy/vacation schedules.
> On Aug 16, 2019, at 15:34, Nick Boldt <nboldt@xxxxxxxxxx> wrote:
> > Two weeks could be not enough. There are people wo have three or more weeks off during summer time. However, mid-end September is a good chance that most summer breaks are over.
> "Mid-end September" is when we GA. If you're not in the train by RC2, you've missed the ferry and will have to wait until the next one arrives at the dock.
Ah right, forgot about that. In this case my opinion is: the opt-in process does not work anymore. IMO it must be possible to participate in the June release and then step aside for a bit without being kicked out in September. A lot open source projects operate by "occasion". They are not full-time staffed. Thus, their might be a release and then a period without activity.
eclipse.org-planning-council mailing list
IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation.Â To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.
Principal Software Engineer, RHCSA
Productization Lead :: CodeReady WorkspacesÂ
IM: @nickboldt / @nboldt / http://nick.divbyzero.com
âThe Only Thing That Is Constant Is Changeâ -ÂHeraclitus