as you most likely remember, we've been there already. The previous
fuel-core group has been split especially due to low number of core
reviewers, too big load on them and inflexibility in promoting valuable
contributors into the group. Worth noting that it was very welcome change.
Breakage of anything is probably the last thing I intended to achieve with
that patch. Maybe I misunderstand how tasks dependencies works, let me
describe *explicit* dependencies I did in tasks.yaml:
hiera requires deploy_start
hiera is required for setup_repositories
Let's drop 3.3 as well. 3.4 is oldschool enough for vintage lovers.
On Thu, Jan 21, 2016 at 11:03 AM, Aleksandr Didenko
> > I also think 3.3 is the version that ships with 14.04.
> 3.4.3 is shipped with Ubuntu-14.04. I think 3.4, 3.8 and 4 should be
I took a glance on Maciej's patch and it adds a switch to tar command to
make it follow symbolic links, so it looks good to me.
On Thu, Jan 14, 2016 at 10:39 AM, Igor Kalnitsky
> Hey Maceij -
> > About hardlinks - wouldn't it be better to use
We don't develop features for already released versions… It should be done
for master instead.
On Tue, Nov 10, 2015 at 7:02 AM, Adam Heczko wrote:
> Do you plan to port your patchset to future Fuel releases?
> On Tue, Nov 10, 2015 at 12:14 AM,
OpenStack Development Mailing List (not for usage questions)
I have no idea if I'm eligible to vote, but I'll do it anyway:
On Thu, Sep 3, 2015 at 9:16 PM, Sergey Vasilenko
> OpenStack Development Mailing List (not
Freezing every moving part is complete overkill and puts a heavy burden on
team as well as infra itself. The fix couldn't be more simple: just put
bounds in requirements.
1) if there is a new conflicting version, you need to set this
upper-bound, thus you need to modify bits which
On Thu, Jul 9, 2015 at 10:24 AM, Matthew Mosesohn mmoses...@mirantis.com
What about bashate? It is already in use in several OpenStack projects?
To be honest, I don't see any value of using bashate. It does some basic
but none of them is
I'll keep it in mind not to create unnecessary backports, although I really
find it more convenient to do them once I submit changes to master for
review. I apologize for , it indeed was wrong and it won't happen again.
On Wed, Mar 11, 2015 at 12:36 AM, Ryan Moe
FYI, xz with multithreading support (5.2 release) has been marked as stable
On Mon, Nov 24, 2014 at 12:32 PM, Bartłomiej Piotrowski
On 24 Nov 2014, at 12:25, Matthew Mosesohn mmoses...@mirantis.com wrote:
I did this
Mail list logo