1:19 p.m.
In the last few days, the Podman development team has been working to
release Podman-1.9.0. This is likely to be the last Podman-1.X release
before we transition to Podman-2.x. We have been working since
November 2019 to make a significant overhaul of Podman’s architecture.
And if we did our job correctly, most casual Podman users will not
notice a difference. We will continue to investigate and fix issues in
Podman-1.x versions but severity of the bug and priority will dictate
our response.
What some users who follow upstream development may notice is that
while we make the final push to a 2.x release, our GitHub repository
will look drastically different. For some period of time, certain
Podman commands, if built based on upstream, may not function exactly
as expected nor even exist. We already know we will need to disable
some of our CI testing framework as part of this final push until we
have a more complete Podman v2.x. We will not release Podman 2.0 until
we are satisfied that it is ready. While upstream development will be
impacted by the announced migration to Podman v2.x, you can still open
issues and contribute pull requests to the project.
As has been the standard with our project, we will remain transparent
in our development activities and try to keep our community appraised
of our progress. We are excited for some of the technical
advancements that Podman v2.x will give our users. Subsequent blog
posts will be written on those advancements and why they matter to our
users.
Brent
2:19 p.m.
On Thu, 16 Apr 2020, Brent Baude wrote:
In the last few days, the Podman development team has been working
to release Podman-1.9.0. This is likely to be the last Podman-1.X
release before we transition to Podman-2.x. We have been working
since November 2019 to make a significant overhaul of Podman’s
architecture. And if we did our job correctly, most casual Podman
users will not notice a difference. We will continue to investigate
and fix issues in Podman-1.x versions but severity of the bug and
priority will dictate our response.
... snip ...
is the 2.0 development stream available? one of the things i'm
interested in doing is helping with the documentation, particularly
since i want to use it as the basis for a course or two. i'm also in
the process of working with sphinx on another project, so the libpod
use of sphinx is convenient.
anyway, is the 2.0 content cloneable?
rday
2:44 p.m.
On 4/16/20 15:19, Robert P. J. Day wrote:
On Thu, 16 Apr 2020, Brent Baude wrote:
> In the last few days, the Podman development team has been working
> to release Podman-1.9.0. This is likely to be the last Podman-1.X
> release before we transition to Podman-2.x. We have been working
> since November 2019 to make a significant overhaul of Podman’s
> architecture. And if we did our job correctly, most casual Podman
> users will not notice a difference. We will continue to investigate
> and fix issues in Podman-1.x versions but severity of the bug and
> priority will dictate our response.
... snip ...
is the 2.0 development stream available? one of the things i'm
interested in doing is helping with the documentation, particularly
since i want to use it as the basis for a course or two. i'm also in
the process of working with sphinx on another project, so the libpod
use of sphinx is convenient.
anyway, is the 2.0 content cloneable?
rday
_______________________________________________
Podman mailing list -- podman(a)lists.podman.io
To unsubscribe send an email to podman-leave(a)lists.podman.io
Not sure what you are asking, but all of out code and docs are opensource.
4:12 p.m.
On Thu, 16 Apr 2020, Daniel Walsh wrote:
Not sure what you are asking, but all of out code and docs are
opensource.
never mind ... was wondering where the v2 stuff was, then just
checked https://github.com/containers/libpod/tree/master, and noticed
15 minutes ago commit on master branch, "Podman V2 birth". i was
expecting a "v2" branch, or something like that. so i'm assuming the
master branch is it.
rday
2:06 p.m.
On 4/16/20 17:12, Robert P. J. Day wrote:
On Thu, 16 Apr 2020, Daniel Walsh wrote:
> Not sure what you are asking, but all of out code and docs are
> opensource.
never mind ... was wondering where the v2 stuff was, then just
checked https://github.com/containers/libpod/tree/master, and noticed
15 minutes ago commit on master branch, "Podman V2 birth". i was
expecting a "v2" branch, or something like that. so i'm assuming the
master branch is it.
rday
_______________________________________________
Podman mailing list -- podman(a)lists.podman.io
To unsubscribe send an email to podman-leave(a)lists.podman.io
Yes we are handling podman 1.9.0 on a branch. Master branch is on to
podman 2.0.0
2:49 p.m.
Robert,
My recommendation would be to wait a few weeks. I have committed to
driving some major changes to the upstream docs. You are now on my list as
the "third amigo" if you are OK with that. I'm planning on creating a
branch to work on docs, along with a development docs site (I need to work
on that). Then, I will reach out, and we can all hack on it. Does that work?
P.S. We have a Read The Docs site today:
https://podman.readthedocs.io/en/latest/Introduction.html
Automatically built from here:
https://github.com/containers/libpod/tree/master/docs/source
Tom Sweeney is planning on adding a link to the RTD site from podman.io
very soon. We have docs, it just needs a lil love, that's all :-)
Best Regards
Scott M
On Thu, Apr 16, 2020 at 3:41 PM Robert P. J. Day <rpjday(a)crashcourse.ca>
wrote:
On Thu, 16 Apr 2020, Brent Baude wrote:
> In the last few days, the Podman development team has been working
> to release Podman-1.9.0. This is likely to be the last Podman-1.X
> release before we transition to Podman-2.x. We have been working
> since November 2019 to make a significant overhaul of Podman’s
> architecture. And if we did our job correctly, most casual Podman
> users will not notice a difference. We will continue to investigate
> and fix issues in Podman-1.x versions but severity of the bug and
> priority will dictate our response.
... snip ...
is the 2.0 development stream available? one of the things i'm
interested in doing is helping with the documentation, particularly
since i want to use it as the basis for a course or two. i'm also in
the process of working with sphinx on another project, so the libpod
use of sphinx is convenient.
anyway, is the 2.0 content cloneable?
rday_______________________________________________
Podman mailing list -- podman(a)lists.podman.io
To unsubscribe send an email to podman-leave(a)lists.podman.io
--
--
[image: Summit Virtual Experience]
<https://www.redhat.com/en/summit?sc_cid=7013a000002D2QxAAK>
Scott McCarty
Product Management - Containers, Red Hat Enterprise Linux & OpenShift
Email: smccarty(a)redhat.com
Phone: 312-660-3535
Cell: 330-807-1043
Web: http://crunchtools.com
Using Azure Pipelines with Red Hat Universal Base Image and Quay.io:
https://red.ht/2TvYo3Y
3:34 p.m.
On Thu, 16 Apr 2020, Scott McCarty wrote:
Robert,
My recommendation would be to wait a few weeks. I have committed
to driving some major changes to the upstream docs. You are now on
my list as the "third amigo" if you are OK with that. I'm planning
on creating a branch to work on docs, along with a development docs
site (I need to work on that). Then, I will reach out, and we can
all hack on it. Does that work?
yup. can i assume it will remain sphinx-based, as i am currently
knee-deep in helping convert another project to sphinx, so being able
to transfer all that know-how would be just ducky.
rday
3:42 p.m.
On Thu, Apr 16, 2020 at 4:34 PM Robert P. J. Day <rpjday(a)crashcourse.ca>
wrote:
On Thu, 16 Apr 2020, Scott McCarty wrote:
> Robert,
> My recommendation would be to wait a few weeks. I have committed
> to driving some major changes to the upstream docs. You are now on
> my list as the "third amigo" if you are OK with that. I'm planning
> on creating a branch to work on docs, along with a development docs
> site (I need to work on that). Then, I will reach out, and we can
> all hack on it. Does that work?
yup. can i assume it will remain sphinx-based, as i am currently
knee-deep in helping convert another project to sphinx, so being able
to transfer all that know-how would be just ducky.
I don't think it was every Sphinx based? The Read The Docs stuff appears to
be in RST format. Where are you seeing Sphinx docs at? I can dig in.
rday
--
--
[image: Summit Virtual Experience]
<https://www.redhat.com/en/summit?sc_cid=7013a000002D2QxAAK>
Scott McCarty
Product Management - Containers, Red Hat Enterprise Linux & OpenShift
Email: smccarty(a)redhat.com
Phone: 312-660-3535
Cell: 330-807-1043
Web: http://crunchtools.com
Using Azure Pipelines with Red Hat Universal Base Image and Quay.io:
https://red.ht/2TvYo3Y
3:48 p.m.
On Thu, 16 Apr 2020, Scott McCarty wrote:
On Thu, Apr 16, 2020 at 4:34 PM Robert P. J. Day <rpjday(a)crashcourse.ca> wrote:
On Thu, 16 Apr 2020, Scott McCarty wrote:
> Robert,
> My recommendation would be to wait a few weeks. I have committed
> to driving some major changes to the upstream docs. You are now on
> my list as the "third amigo" if you are OK with that. I'm
planning
> on creating a branch to work on docs, along with a development docs
> site (I need to work on that). Then, I will reach out, and we can
> all hack on it. Does that work?
yup. can i assume it will remain sphinx-based, as i am currently
knee-deep in helping convert another project to sphinx, so being able
to transfer all that know-how would be just ducky.
I don't think it was every Sphinx based? The Read The Docs stuff
appears to be in RST format. Where are you seeing Sphinx docs at? I
can dig in.
i'm looking at libpod/docs/Makefile:
# Minimal makefile for Sphinx documentation
#
# You can set these variables from the command line, and also
# from the environment for the first two.
SPHINXOPTS ?=
SPHINXBUILD ?= sphinx-build
SOURCEDIR = source
BUILDDIR = build
# Put it first so that "make" without argument is like "make help".
help:
@$(SPHINXBUILD) -M help "$(SOURCEDIR)" "$(BUILDDIR)"
$(SPHINXOPTS) $(O)
clean:
rm -fr build/
.PHONY: help Makefile
# Catch-all target: route all unknown targets to Sphinx using the new
# "make mode" option. $(O) is meant as a shortcut for $(SPHINXOPTS).
%: Makefile
@$(SPHINXBUILD) -M $@ "$(SOURCEDIR)" "$(BUILDDIR)"
$(SPHINXOPTS) $(O)
~
if you're not using sphinx, i am massively confused.
rday
1710
days inactive
1711
days old
8 comments
4 participants
participants (4)
-
Brent Baude -
Daniel Walsh -
Robert P. J. Day -
Scott McCarty