duplicity-team team mailing list archive

[Kenneth Loafman <kenneth@xxxxxxxxxxx>]

I never got around to answering this.  I've been busy.  Sorry.

I really should make at least one more 0.6 release with some fixes, then
concentrate on 0.7.  I've held off on 0.7 because I was not sure which
direction it should go, but it really does need to either get scrubbed,
or get developed.  I think it should be developed.  The par2 stuff is in
there, but it really should be tested and expanded.

As to snapshot tarballs, that would be nice.  Is that something we could
set up on LP for nightly or weekly builds.  Could it be triggered only
if there was a change?

As to time based releases, I've thought about trying to put out a stable
version N weeks before the Ubuntu release cycle, with potentially some
intermediate releases when bugs are fixed.  How far before release would
that commit have to be made?

...Ken

Michael Terry wrote:
> Hello, Ken!  I was curious about the plans around 0.7 and the timing
> of its eventual release.  Thinking about it loaded me with questions.
> So here I go.
> 
> I know it has enhanced parity/checksum checking or some such?  Are
> there features we are waiting to bake or just waiting for the existing
> features to be adequately tested?
> 
> I wonder how many people test 0.7.  I don't know what kind of people
> would use a development snapshot for their backup data.  I don't think
> even I would.  :)
> 
> Do you think if you released development snapshot tarballs, if it
> would increase testing?
> 
> Have you ever considered time based releases, with many development
> releases leading up to a stable release?
> 
> I've been doing that with Deja Dup (borrowing GNOME's 6-month
> schedule) and it's been good so far.  Forces a kind of feature period
> followed by a baking period before stable release.  But it can mean
> more maintainer work, if you release as many snapshots as GNOME does
> (like 1.5/month).
> 
> -mt
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~duplicity-team
> Post to     : duplicity-team@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~duplicity-team
> More help   : https://help.launchpad.net/ListHelp
>

Attachment: signature.asc
Description: OpenPGP digital signature