in the bump (from a fl:2 user point of view when updating) python
changes and conary changes and toolchain changes, at same time,...
i just want to avoid that for the common case the probabilities of ppl
getting stuck in a state where they can't neither rollback nor mv
forward are absolutely minima
On Fri, Mar 25, 2011 at 7:08 PM, Alexandre Franke
wrote:
>> Instead of releasing 2.5 from fl:2-qa, the
>> other option is to push to fl:2, release from there (as in the past),
>> and (possibly) break the upgrade path for those users.
>
> Sorry for being naive, but I don't see why this will break u
On Fri, Mar 25, 2011 at 8:13 AM, Jesse Zhang wrote:
> Hi,
Hi,
> Instead of releasing 2.5 from fl:2-qa, the
> other option is to push to fl:2, release from there (as in the past),
> and (possibly) break the upgrade path for those users.
Sorry for being naive, but I don't see why this will break
Hi,
I think we never really brought this up on the mailing list: what should
we do about the upgrade path for current fl:2 users?
There have been some consensus that the 2.5 release is to be done from
the fl:2-qa branch. But it has problems. When someone installs 2.5, they
will be on the qa branc
