Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [winery-dev] Pre-Releases


per co-incidence, the same question was rised at the incubation mailing list with a very positive answer (see below).

* Mail source:
* Developer handbook will be updated:



---------- Forwarded message ----------
From: Ed Merks <ed.merks@xxxxxxxxx>
Date: 2017-07-06 11:24 GMT+02:00
Subject: Re: [incubation] Release process
To: incubation@xxxxxxxxxxx


Just do no call it a release.  Don't use that word to describe what you've making available/redistributing.  Of course almost all projects do nightly, integration, milestone, and release candidate builds and make those available as p2 update sites or otherwise for their consumers.  You can do the same.  A release review is only required to produce a release and you can do that when you feel the code is in a quality state that you feel comfortable can be represented as a stable release for your consumers.


2017-07-03 17:21 GMT+02:00 Oliver Kopp <>:
Dear mentors,

I am still in preparation of a release of Winery. I checked and wonder whether
and how pre-releases are possible.

Setting: In a project, I want to version Winery and give away
snapshots. Taken, I want to release v2.0.0, I assume, I can "release"
v2.0.0-SNAPSHOT-2017-07-03. Including a respective tag on github to be
able to distribute a compiled snapshot and the corresponding source
code. For sure, not (fully) IP checked and not an official release.

I searched also
and found "A Project in the Incubation Phase with two Mentors may make
a pre-1.0 Release", but I do not find, what is the condition and the
process for such a release.

Does someone know how to do that? Or should I distribute full releases
only? But I'd like to distribute development snapshots somehow...



Back to the top