On 18-02-12 16:13:30, William M Edmonds wrote:
> I'm not seeing a stable/queens branch for openstack/requirements yet. Is
> that not what you meant? When is that projected?
>
> Matthew Thode wrote on 02/12/2018 11:25:44 AM:
> > This means we are back to business as usual.
This means we are back to business as usual.
cycle trailing projects have been warned not to merge requirements
updates until they branch or get an ack from a requirements core.
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
mp;q=translator&type=
https://github.com/openstack/murano/search?utf8=%E2%9C%93&q=translator&type=
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
__
OpenStack Development Mailing L
g said that if the project hasn't had any updates at all since it's
> >> creation in July 2017 perhaps it's no longer needed and could be
> >> removed?
> >>
> >
> > We do plan to use it, we just never had time to
) I'd
appreciate it, would give us some peace of mind to unfreeze tomorrow.
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
On 18-02-08 15:20:54, Matthew Thode wrote:
> The following do not have a stable/queens branch and could cause
> requirements to remain frozen until they do. If I get no response by
> tomorrow afternoon my time (about 24 horus from the time this email was
> SENT) I may still move
ircle tricircle
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstac
> See you soon!
> >
> > - Kendall Nelson (diablo_rojo)
> >
> > [1]
> > https://docs.google.com/spreadsheets/d/1J2MRdVQzSyakz9HgTHfwYPe49PaoTypX66eNURsopQY/edit?usp=sharing
> >
And Requirements after that (at 2:20 Thursday)
--
Matthew Thode (prometheanfire)
signature.asc
Description:
Updated from global requirements
> +* Updated from global requirements
>
>
> The requirements changes are removal of mox, and fix for oslotest to
> sync the queens level requirements. so this looks good to me. +1
>
Yep, LGTM as well (just approved)
--
#n1539
> >
> > __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > http://l
scheduled
> on the Tuesday. How much time would we need ? I was thinking we could
> use only Tuesday afternoon.
>
> [1] https://etherpad.openstack.org/p/PTG-Dublin-missing-topics
>
I'll make myself available with both my requirements and distro
packaging hats.
--
Matth
On 18-02-07 16:33:52, Luke Hinds wrote:
> On Wed, Feb 7, 2018 at 4:23 PM, Matthew Thode
> wrote:
>
> > Hi all,
> >
> > it looks like some of your projects may need to cut a queens
> > branch/release. Is there anything we can do to move it along?
> >
> &
tricircle tricircle
vitragevitrage
watcherwatcher
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP
>
It should have time to get in for the freeze, the question I have is
'What in openstack is broken if we update upper-contraints after the
freeze instead of before?'
A follow up question is 'does this need a global-requirements.txt bump?'
+2 from me on the UC bum
re freeze period for libraries to avoid this.. But it
> cannot be introduced with the current library release freeze. Another PTG
> topic? :)
>
As discussed on IRC you have my ack
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
__
s require a gr bump even more now, which would
cause client re-releases iirc. My question has more to do with having
this not happen again. Do you cross gate with other projects (clients)?
That would allow you to check what's going into your master with what's
in the
On 18-02-02 18:02:38, Terry Wilson wrote:
> On Fri, Feb 2, 2018 at 4:30 PM, Matthew Thode
> wrote:
> > On 18-02-02 15:59:42, Terry Wilson wrote:
> >> ovsdbapp 0.9.1 (review https://review.openstack.org/#/c/539489/) has a
> >> gate-fixing one-line fix (https://r
Is this just for upper-constraints.txt or for global-requirements.txt as
well?
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questio
magnumclient to new release 2.8.0
> update constraint for tosca-parser to new release 0.9.0
> update constraint for python-tackerclient to new release 0.11.0
> update constraint for python-heatclient to new release 1.14.0
>
your time,
Matthew Thode
IRC: prometheanfire
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev
re due to the nature of the library, this should probably first be
> proposed as a change to openstack/requirements and discussed there...
>
> When it's ready but blocked by FF we can return to a ML thread to
> discuss it...
>
Thanks for the link, and yes should proba
lient is published at pypi this
> morning.
>
> 1. https://review.openstack.org/#/c/539126/
>
LGTM, +2
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
__
OpenStack Development Mail
po.
The licence looks like gplv3, which is fine for non-openstack code.
There's also no commit since the initial commit.
Unless I'm looking at the wrong repo, I'm going to say no to this FFE.
https://github.com/lschw/pyspdf
--
Matthew Thode (prometheanfire)
signature.asc
Descripti
On 18-01-29 14:44:20, Matthew Thode wrote:
> On 18-01-28 20:47:42, Matthew Thode wrote:
> > On 18-01-27 21:37:53, Matthew Thode wrote:
> > > On 18-01-26 23:05:11, Matthew Thode wrote:
> > > > On 18-01-26 00:12:38, Matthew Thode wrote:
> > > > &
On 18-01-28 20:47:42, Matthew Thode wrote:
> On 18-01-27 21:37:53, Matthew Thode wrote:
> > On 18-01-26 23:05:11, Matthew Thode wrote:
> > > On 18-01-26 00:12:38, Matthew Thode wrote:
> > > > On 18-01-24 22:32:27, Matthew Thode wrote:
> > > > &
l need to land as well that don't appear to be covered in
> the requirements cross jobs.
>
Added them as depends-on to https://review.openstack.org/538549
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
On 18-01-27 21:37:53, Matthew Thode wrote:
> On 18-01-26 23:05:11, Matthew Thode wrote:
> > On 18-01-26 00:12:38, Matthew Thode wrote:
> > > On 18-01-24 22:32:27, Matthew Thode wrote:
> > > > On 18-01-24 01:29:47, Matthew Thode wrote:
> > > > &
On 18-01-26 23:05:11, Matthew Thode wrote:
> On 18-01-26 00:12:38, Matthew Thode wrote:
> > On 18-01-24 22:32:27, Matthew Thode wrote:
> > > On 18-01-24 01:29:47, Matthew Thode wrote:
> > > > On 18-01-23 01:23:50, Matthew Thode wrote:
> > > > > Requi
On 18-01-26 00:12:38, Matthew Thode wrote:
> On 18-01-24 22:32:27, Matthew Thode wrote:
> > On 18-01-24 01:29:47, Matthew Thode wrote:
> > > On 18-01-23 01:23:50, Matthew Thode wrote:
> > > > Requirements is freezing Friday at 23:59:59 UTC so any last
> > >
ated to my changes:
> >>
> >> error: can't copy 'etc/glance-image-import.conf': doesn't exist or
> >> not a regular file
> >>
> >> I noticed that two other changes [2][3] failed with the same error.
> >>
> >&
On 18-01-24 22:32:27, Matthew Thode wrote:
> On 18-01-24 01:29:47, Matthew Thode wrote:
> > On 18-01-23 01:23:50, Matthew Thode wrote:
> > > Requirements is freezing Friday at 23:59:59 UTC so any last
> > > global-requrements updates that need to get in need to get in n
On 18-01-24 01:29:47, Matthew Thode wrote:
> On 18-01-23 01:23:50, Matthew Thode wrote:
> > Requirements is freezing Friday at 23:59:59 UTC so any last
> > global-requrements updates that need to get in need to get in now.
> >
> > I'm afraid that my condition h
On 18-01-23 01:23:50, Matthew Thode wrote:
> Requirements is freezing Friday at 23:59:59 UTC so any last
> global-requrements updates that need to get in need to get in now.
>
> I'm afraid that my condition has left me cold to your pleas of mercy.
>
Just your daily reminder
Requirements is freezing Friday at 23:59:59 UTC so any last
global-requrements updates that need to get in need to get in now.
I'm afraid that my condition has left me cold to your pleas of mercy.
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP sign
on Monday-Tuesday
> to discuss "hot" last-minute cross-project issues -- if you have ideas
> of topics that we need to discuss in-person, please let us know.
>
As one of the teams in orange, what specific steps, if any
[3] https://github.com/openstack/releases/blob/master/deliverabl
> >> es/queens/oslo.serialization.yaml
> >>
> >>
> >> Actions:
> >>
> >> Block oslo.serialization version 2.21.2, 2.22.0, 2. 23.0in
> >> https://review.openstack.or
On 18-01-17 01:25:10, Matthew Thode wrote:
> So get your changes in or get left behind :D
>
Just to be clear, the HARD deadline for the freeze will be Friday
January 26th at 23:59:59 UTC
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP sig
So get your changes in or get left behind :D
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
On 18-01-16 19:12:16, ChangBo Guo wrote:
> What's the issue for Glance, any bug link ?
>
> 2018-01-16 0:12 GMT+08:00 Matthew Thode :
>
> > On 18-01-13 00:41:28, Matthew Thode wrote:
> > > https://review.openstack.org/531788 is the review we are seeing it in,
On 18-01-13 00:41:28, Matthew Thode wrote:
> https://review.openstack.org/531788 is the review we are seeing it in,
> but 2.22.0 failed as well.
>
> I'm guessing it was introduced in either
>
> https://github.com/openstack/oslo.serialization/commit/c1a7079c26d27a2e46cca2
ommit/cdb2f60d26e3b65b6370f87b2e9864045651c117
--
Matthew Thode
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstac
date. IIRC, for ubuntu they
use cloud-archives to get the right version of libvirt, does something
like that exist for centos/redhat?
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
On 17-12-20 10:56:50, Matthew Thode wrote:
> On 17-12-20 15:51:17, Afek, Ifat (Nokia - IL/Kfar Sava) wrote:
> > Hi,
> >
> > There is an open bug in launchpad about the new release of Networkx 2.0,
> > that is backward incompatible with versions 1.x [1].
> > Is th
hat'd need to be updated.
http://codesearch.openstack.org/?q=networkx&i=nope&files=.*requirements.*&repos=
I'm open to uncapping networkx if these projects have buyin.
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
ation detail, is the
> strongest arguement i have for shared version control of it.
>
So what happens when someone wants to use gunicorn or add another wsgi server
to be tracked by the requirements repo? One of the the things we are around
for is so projects know what library to use for X.
_
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
&
lopment Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Meant to reply from this address, but below is my original response.
The first question I have is if AL
nt Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
The first question I have is if ALL the drivers are suposed to be co-installable
with eachother. If s
gt; changes
> > ACTIONS: Projects merge .gitreview and
> > UPPER_CONSTRAINTS changes
> > ACTIONS: Make sure master publishes {rocky,master}.txt
> > (optionally add the S release at this point,
> > it doe
we would need to update
> > master. This is a point of confusion that we'll need to document and
> > possible check for somewhere in our tools.
> >
> > Yours Tony.
> >
> > [1] This just occurred to me
>
> __
m
> what we're doing now, where constraints are updated as soon as the git
> cache is updated.
>
> I think we should publish using a post-merge job. The job isn't
> expensive, right? It's just copying some files out of git onto the
> web server?
>
> Do we rea
ints.txt from the url only
pros - post
* upper-constraints are available via published location immediately
* sets good precident for end users/devs to use it
cons - post
* both breaks and fixes quick
* more load on infra to publish (2
for it now.
>
> Those constraints files would never be removed but they'd stop getting
> updated when we EOL the requirements branch.
>
> How does that sound?
>
> Yours Tony.
That's correct, I haven't had time this week to create the jobs quite
yet, but hop
t's worth the
effort as an EOL'd and now unbranched project. We could create a
temporary branch from the commit and retag, but as a rule we should not
use the same tag twice (removing the pointer that existed and
On 17-08-29 15:58:55, Jeremy Stanley wrote:
> On 2017-08-29 10:30:42 -0500 (-0500), Matthew Thode wrote:
> [...]
> > 3. reversion. Start new versions at 3000 or something, kinda
> > dirty imo.
>
> And sort of a 3.1 option is to prepend a PEP 440 version epoch:
>
>
rg/cgi-bin/mailman/listinfo/openstack-dev
I think we have three options here.
1. Unpublish. This is probably the simplest, but generally goes against
the policy of pypi to never unpublish things (it is not a hard and fast
rule though).
2. Rename. A bunch of work for downstreams but
v-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
We use it downstream to build ironic images using the process kevin
documented here.
https://cloudnull.io/2016/11/osic-building-baremetal-ironic-images/
It can probably b
channel.
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
___
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Matthew Thode (prometheanfire
ch if you can though.
If you have questions, feel free to reach out to me on irc
(prometheanfire on freenode, #openstack-requirements for the channel) or
email.
--
Matthew Thode (prometheanfire)
signature.asc
Descri
The current plan is to thaw requirements on Monday. If that happens
you'll need to be very careful in reviewing any bot updates from our
master (queens) to your master (pike).
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
___
e will
> be added to the core group in a few days.
>
> --
> Best,
> Samuel Cassiba
>
I haven't worked with him in an openstack chef way, but I've worked with
him through the OSUOSL. He's always been great to work with. IIRC the
OSUOSL also uses chef to deploy op
On 17-08-08 08:03:42, Matthew Thode wrote:
> On 17-08-08 16:11:53, Renat Akhmerov wrote:
> > Hi,
> >
> > We recently sent a patch [1] to release the version 3.1.2 of
> > python-mistralclient out of Pike branch. It was done after the date of
> > final client
s)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
It sounds like you will need a requirements update as well, both UC and
maybe GR. GR would suck at this VERY late point. The cur
time,
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
subscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
This is fine with me, it's not used anywhere at the moment so doesn't
look to have any knockon effects.
http://
ease release this and take the new version in for requirements repo,
>
> https://review.openstack.org/490001
>
> Andreas
Looks fine here, are you looking for just a UC bump?
--
Matthew Thode (prometheanfire)
signatu
7;t see anything that worries me.
>
> From a requirements POV I'm +2 on a u-c bump -2 on a g-r bump.
>
> Yours Tony.
Agreed, the amount of projects that'd be impacted by a GR bump is too
high, but a UC bump is fine.
--
Matthew Thode (prometheanfire)
signature.asc
Descript
only affects a small
> number of projects, so the risk is fairly small.
>
> I assume you've done enough testing to feel comfortable that 4.5.2 will
> work better than 4.5.0 and 4.5.1?
>
> Doug
>
> ___
opment Mailing List (not for usage questions)
> > > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> > >
> >
>
>
t'd be good to be in sync. The
same could be said to many of the bumps that go through the requirements
project. One of the things we've been working on is divergent
requirements, where the goal is to keep making sure all projects test
against one set of upper-constraints, b
lman/listinfo/openstack-dev
>
>
>
> --
> Davanum Srinivas :: https://twitter.com/dims
>
> ______
> OpenStack Development Mailing List (not for usage ques
ck
> projects and their deliverables.
>
> A huge improvement from where PTLs in Mitaka and prior were manually
> tagging and signing deliverables, handling the release note process, and
> all other sorts of minutia that required extreme care and focus.
>
> A fine example of
Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> <http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
>
>
>
>
&g
On 05/30/2017 04:08 PM, Emilien Macchi wrote:
> On Tue, May 30, 2017 at 8:36 PM, Matthew Thode
> wrote:
>> We have a problem in requirements that projects that don't have the
>> cycle-with-intermediary release model (most of the cycle-with-milestones
>> mod
obably want to add a review criteria to the requirements list that
> projects using the cycle-with-milestone model are not added to the list
> to avoid this issue in the future.
>
> Doug
>
> ______
> OpenStack
on irc as prometheanfire in the #openstack-requirements channel.
--
Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubs
https://review.openstack.org/#/q/project:openstack/requirements+status:open+NOT+branch:master
We currently do not have anyone able to review/workflow these items and
it'd be nice if we could get some eyes on these reviews.
Thanks,
--
Matthew Thode (prometheanfire)
signature.asc
Descri
s pbr.
mistral
os-apply-config
os-collect-config
os-refresh-config
os-vif
If these projects could make a release (something fetchable by pypi) off
of master that's all that's needed. They all have updated their
requirements in master, just no consumable release.
--
Matthew Thode
do stuff that
> upstream can't (or won't) do.
>
> Chris
Us distro folks don't like it either :P
--
Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
cific timeframe?
>
> Thanks for surfacing it Matthew.
>
> -amrith
Heh, thanks, I suspect a few things are fairly cross project for
requirements. Moving to new webob / eventlet / sqlalchemy for instance.
Is there a specific process we go through to do these?
--
Matthew Thode (prome
dome+owner:dims-v
>
> Thanks,
> Dims
>
> On Wed, Mar 8, 2017 at 2:03 PM, Matthew Thode
> wrote:
>> So, pycrypto upstream is dead and has been for a while, we should look
>> at moving off of it for both bugfix and security reasons.
>>
>> Currently it
he
affected projects.
--
Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...
gt;>> 3) Keep diskimage-builder under tripleo (EmilienM PTL).
> We don't want to carry this one anymore for the reasons mentioned in
> that thread.
>
As a sometimes contributor to DIB for Gentoo stuff I'm fine with moving
it out into it's own project under the big tent,
, even if it's done perfectly. If
it's not done perfectly we have to deal with untangling the requirements
for a security update (or the like).
--
Matthew Thode (prometheanfire)
signature.asc
Descripti
After a short delay for reasons Openstack is now up to date on Gentoo.
Just `emerge =sys-cluster/openstack-meta-2017.1.` with your desired
use flags to pull in the head of the services stable branches and their
dependencies.
--
Matthew Thode (prometheanfire)
signature.asc
Description
rest of openstack (and we'd have to
remove you from gr-updates eventually as well).
>
> Thanks!
>
>
> [1] https://github.com/openstack/requirements
> [2] https://github.com/openstack/nova-dpm
> [3] https://github.com/openstack/networking-dpm
> [4] https://github.com/open
will need to
talk about the GR update, if it's requested.
--
Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
On 01/31/2017 12:18 PM, Gary Kotton wrote:
> Hi,
> At the moment we are the only consuming project. This is blocking us at the
> moment. How do you suggest moving this forwards?
> Could we remove the upper constraints?
> Thanks
> Gary
>
> On 1/31/17, 6:48 PM, "Matth
e process goes like this.
1. Update UC
2. Update GR
If subscribed to requirements
3. networking-dpm gets an update automatically when the periodic runs
else
3. networking-dpm needs a manual update, can occur before GR update.
--
Matthew Thode (prometheanfire)
ects, causing every consuming project to have to
re-release. I'd need buy-in from them before I consider allowing the
gr-update through, though I'm generally fine with the UC update.
--
Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
___
his is a new minimum. That is likely fine, based on it only actually
being required by the networking-dpm project, though I'd require an ack
from them to get a GR bump considered.
--
Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
__
fo/openstack-dev
>
This'll impact neutron as well and I'd like their ack on this. Though
it generally looks fine to me.
--
Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
picked
> to stable/ocata. Let's please update the upper-constraints with this
> new version.
>
> Thanks,
> Dims
>
UC only is fine with me
--
Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
___
On 01/30/2017 03:24 AM, Dmitry Mescheryakov wrote:
> Hello Matthew,
>
> I see that you have frozen my
> CR https://review.openstack.org/#/c/425132/ , but it is for
> stable/newton. Should not freeze apply to master only?
>
> Thanks,
>
> Dmitry
>
Yep, fixed, s
On 01/24/2017 02:22 PM, Matthew Thode wrote:
> We are going to be freezing Thursday at ~20:00 UTC.
>
> So if you need any changes we'll be needing needing them in soon, with
> reasoning. Thanks.
This is just about 4 hours away now, so second and last reminder.
--
Matthew Thod
On 01/24/2017 09:57 PM, Matthew Thode wrote:
> Basically I'd like to ask the docs people if they are fine with updating
> the minimum version of sphinx from sphinx>=1.2.1,!=1.3b1,<1.4 to
> sphinx>=1.5.1. This change seems fairly major, especially given that
> there
ersions.
I'd appreciate docs team reviews on this. We plan on having a meeting
soon at 10:00 UTC in #openstack-meeting-alt if you care to join.
https://review.openstack.org/418772
--
Matthew Thode (prometheanfire)
signature.asc
h should also be the minimum version.
That's fine, I think we expected you to be a little late considering
what you consume.
--
Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
__
Open
We are going to be freezing Thursday at ~20:00 UTC.
So if you need any changes we'll be needing needing them in soon, with
reasoning. Thanks.
--
Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital sign
101 - 200 of 320 matches
Mail list logo
