GTimeLog

Bug #628873
Comment #5

Comment 5 for bug 628873

Revision history for this message

Marius Gedminas (mgedmin) wrote on 2010-09-02: Re: [Bug 628873] Re: Alternative configuration directory

On Thu, Sep 02, 2010 at 05:47:23PM -0000, Barry Warsaw wrote:
> What do you think about doing a release soon?

Sure. There's one minor outstanding issue that I'd like to get fixed
before releasing 0.4.0:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595280

> I'd like to get updated
> versions into Debian and Ubuntu eventually.

That would be awesome. The Debian package is currently orphaned. I
once tried to build an updated version, but it turned out to be more
difficult than I'd thought.

> Both are in feature freeze,
> but I'd be happy to update the packaging and throw it into a PPA.
> Either mine or ~gtimelog-dev if we create one.

Yay!

> If you give me upload
> rights to the cheeseshop project, I'm happy to take care of it all.

It's no big deal; 'make release' automates most of it.

What's your PyPI username?

On Thu, Sep 02, 2010 at 05:48:47PM -0000, Barry Warsaw wrote:
> Oh, one other thing. I'd like to upgrade the trunk branch to 2a format.

Upgraded.

> It'll make merges and other tasks *so* much easier. Again, happy to
> take care of it if you approve. It will mean that you'll have to re-
> branch the trunk,

Sounds ominous. I can still 'bzr pull' from lp:gtimelog, and 'bzr
upgrade' in my local tree removed on-the-fly conversion warnings.

> and any stacked branches will be broken, but I think
> the practical impact of that will be minimal.

I don't think there are any stacked branches created on top of
lp:~gtimelog-dev/gtimelog/trunk.

There are stacked branches on top of lp:~mgedmin/gtimelog/trunk. This
exposes an interesting bug/misfeature in Bazaar/Launchpad: When I
changed the owner of the lp:gtimelog branch, the real URL changed from
~mgedmin to ~gtimelog-dev, and all other branches that were stacked on
it became broken. I had to explicitly bzr push
lp:~mgedmin/gtimelog/trunk to make other branches work.

Anyway, lp:~mgedmin/gtimelog/trunk is still using the old format, and I
can still push to it.

Marius Gedminas
--
And yes, you'd be insane to consider C++ for a new project in 2007.
-- Thomas Ptacek

On Thu, Sep 02, 2010 at 05:47:23PM -0000, Barry Warsaw wrote:
> What do you think about doing a release soon?

Sure.  There's one minor outstanding issue that I'd like to get fixed
before releasing 0.4.0:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595280

> I'd like to get updated
> versions into Debian and Ubuntu eventually.

That would be awesome.  The Debian package is currently orphaned.  I
once tried to build an updated version, but it turned out to be more
difficult than I'd thought.

> Both are in feature freeze,
> but I'd be happy to update the packaging and throw it into a PPA.
> Either mine or ~gtimelog-dev if we create one.

Yay!

> If you give me upload
> rights to the cheeseshop project, I'm happy to take care of it all.

It's no big deal; 'make release' automates most of it.

What's your PyPI username?

On Thu, Sep 02, 2010 at 05:48:47PM -0000, Barry Warsaw wrote:
> Oh, one other thing.  I'd like to upgrade the trunk branch to 2a format.

Upgraded.

> It'll make merges and other tasks *so* much easier.  Again, happy to
> take care of it if you approve.  It will mean that you'll have to re-
> branch the trunk,

Sounds ominous.  I can still 'bzr pull' from lp:gtimelog, and 'bzr
upgrade' in my local tree removed on-the-fly conversion warnings.

> and any stacked branches will be broken, but I think
> the practical impact of that will be minimal.

I don't think there are any stacked branches created on top of
lp:~gtimelog-dev/gtimelog/trunk.

There are stacked branches on top of lp:~mgedmin/gtimelog/trunk.  This
exposes an interesting bug/misfeature in Bazaar/Launchpad: When I
changed the owner of the lp:gtimelog branch, the real URL changed from
~mgedmin to ~gtimelog-dev, and all other branches that were stacked on
it became broken.  I had to explicitly bzr push
lp:~mgedmin/gtimelog/trunk to make other branches work.

Anyway, lp:~mgedmin/gtimelog/trunk is still using the old format, and I
can still push to it.

Marius Gedminas
-- 
And yes, you'd be insane to consider C++ for a new project in 2007.
                -- Thomas Ptacek