I think it’s good to create the release records in the portal to publish releases so that users can find this information for all projects in a uniform way. Also PMI provides some automation which I find useful.
Though the mandatory review period and the small number of review slots (2 per month) Is in the way of fast release cycles. Maybe we could get rid of the rigid release review process and replace it by a more flexible one based on lazy consensus on a release review mailing list. E.g. project publishes release records and IP log on release review mailing list and asks for release review (not on the current fixed bi-weekly schedule, but at any date). If PMC accepts the release and no one else objects on the release review list within e.g. 3 days the review is considered successful and the release can be published. -Matthias From: <[email protected]> on behalf of Mickael Istria <[email protected]> Reply-To: Discussions for new Eclipse projects <[email protected]> Date: Wednesday, 28. March 2018 at 17:09 To: Discussions for new Eclipse projects <[email protected]> Subject: Re: [incubation] Fast releasing projects On Wed, Mar 28, 2018 at 4:52 PM, Gorkem Ercan <[email protected]<mailto:[email protected]>> wrote: Isn’t the Release notes (the new & noteworthy) a better format the outsiders audience? Probably. However at the moment, I don't think such N&N external documents are sustainable enough (in term of URL location and so on) to meet the quality criteria of typical Eclipse governance.
_______________________________________________ incubation mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/incubation
