On Mon, Jan 20, 2014 at 12:39:52PM +0100, Karel Piwko wrote:
On Mon, 20 Jan 2014 12:27:22 +0100
Matthias Wessendorf <matzew(a)apache.org> wrote:
> On Mon, Jan 20, 2014 at 12:17 PM, Karel Piwko <kpiwko(a)redhat.com> wrote:
>
> > > +1 on postponing to a later point. If ready by April, should be fine as
> > > well (my opinion). Bruno had a good point, that the postponed release
> > > should not stop us from releasing (unstable) snapshots for testing
> > reasons.
> > > I like that: Release often, release early.
> >
> > What is actually an (unstable) snapshot? Could you shed more light on that?
> >
>
> I'd say a regular snapshot, from master branch, released to the snapshot
> repo
That's good until another project(s) will rely on it. You update snaphot and
other projects will get broken without any option to avoid that. It would be
much better to make snapshots stable in time, as I described in previous email.
Well, that's how snapshots work. We can't fix people not getting it,
unfortunately :(
--
qmx