[IPython-dev] IPython1 versioning conventions
Ville M. Vainio
Thu Feb 21 02:01:03 CST 2008
Fwd to list.
On Thu, Feb 21, 2008 at 1:54 AM, Brian Granger <email@example.com> wrote:
> On Wed, Feb 20, 2008 at 4:13 PM, Ville M. Vainio <firstname.lastname@example.org> wrote:
> > On Thu, Feb 21, 2008 at 12:52 AM, Brian Granger <email@example.com> wrote:
> > > How should we version IPython1? Should it have versions that:
> > >
> > > 1) Are somehow related to those of trunk IPython? (the current scheme
> > > suggests something like that).
> > > 2) Are completely independent?
> > +1 for completely independent, the relationship hardly exist at this
> > point (it has not started to swallow the trunk code yet).
> OK, I think this is a good idea.
> > > I think our current thought is that when IPython1 reaches version 1.0,
> > > it would become a full replacement for IPython trunk (which would
> > > itself disappear). But that is still a ways off.
> > Yes, it is. Try something like 0.3, and we can start upping it when
> > it's starting to close in at feature parity with trunk.
> This sounds good to me. 0.1/0.2 would suggest that IPython1 was brand
> new, which isn't true.
> > How about creating that ipython1 project in launchpad now? I don't
> > think we should have those branches in IPython project, it gets kinda
> > messy as the code bases are not related (yet).
> What branches. You probably mean the old saw/chainsaw branches.
> Those are long dead, and for a while now we have been working from a
> top-level ipython1 repo that has its own branches/tags:
> But, I am getting close to creating an ipython1 lp branch. My plans
> are as follows:
> * Finish updating the documentation to reflect the recent changes I
> have been making
> * Merge back into the ipython1 trunk.
> * update the version of ipython1 to 0.3
> * Create a launchpad branch for ipython1
> * Make an announcement to ipython-dev about this.
> In other news, I have a good start of setting up a really nice way of
> using RST files for documentation. I am almost done converting the
> ipython1 docs to this format. This should make things much easier for
> all of us.
> More details to follow.
Excellent! I have been waiting for this, and can start fixing the docs
for ipython-stable as well...
Ville M. Vainio - vivainio.googlepages.com
blog=360.yahoo.com/villevainio - g[mail | talk]='vivainio'
More information about the IPython-dev