[Pkg-puppet-devel] Are we ok with the state of 0.25.0 ?

[Micah Anderson]

* Nigel Kersten <nigel at explanatorygap.net> [2009-09-25 22:04-0400]:
> On Fri, Sep 25, 2009 at 6:38 PM, Micah Anderson <micah at riseup.net> wrote:
> > * Nigel Kersten <nigel at explanatorygap.net> [2009-09-25 19:29-0400]:
> >> I'd like to get a package uploaded (andy pollock said he'd sponsor it)
> >> for 0.25.0, particularly given 0.25.1 is about to be released....
> >>
> >> Are we ok with the current status? git-buildpackage is working which is cool.
> >
> > I haven't been able to deploy this in my environment, but I did build
> > and install the package and it seemed good.
> >
> > Would it be better to wait for 0.25.1 before pushing it out? I'm not
> > suggesting we should, just wondering.
> 
> I'm not sure either. To be honest, I'm still coming to grips
> personally with the best practices for packaging on Debian :)
> 
> Should we regularly upload packages that are likely to be superseded
> quickly? It doesn't seem ideal, but I'd like people to give this a
> quick run through before we release 0.25.1 as a deb

I think that there are a few issues to consider, do we know what the
issues are in 0.25, that are slated to be fixed by 0.25.1, do we have an
expected timeframe? Can we make a strategic decision based on that
knowledge? Are there fixes for 0.25.1 that already exist in upstream's
repository that can be cherry-picked in to our 0.25, thus limiting the
exposure to issues? There have been plenty of puppet debian package
releases that have included cherry-picking of upstream fixes.

Or, if the issues are minor and would not be a cause for lots of
overhead in dealing with bug reports, then it seems fine.

> I really like having git-buildpackage work. It should make it simpler
> for people to be bleeding edge if they need to.

I'm really glad this got sorted out, I haven't tried to go through the
same steps you have yet, so my brain isn't fully wrapped around how this
works, or why. I'm afraid that when I do need to do this, I will have to
dig through the mailing list archives and try to reconstruct the steps
based on what folks reported here... it might be better if we maintained
a page to preserve these details, maybe on wiki.debian.org?

micah
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20090926/cbe6c1d5/attachment.pgp>