next changelogs and ppa uploads

[Scott Kitterman]

On Monday, September 22, 2014 13:54:04 Harald Sitter wrote:
> On Mon, Sep 22, 2014 at 1:47 PM, Scott Kitterman <ubuntu at kitterman.com> 
wrote:
> > On Monday, September 22, 2014 13:41:32 Harald Sitter wrote:
> >> On Mon, Sep 22, 2014 at 1:18 PM, Scott Kitterman <ubuntu at kitterman.com>
> > 
> > wrote:
> >> > On Monday, September 22, 2014 12:12:36 Harald Sitter wrote:
> >> >> I'd like to propose that *all* ppa uploads of next workspace get a
> >> >> changelog entry.
> >> >> 
> >> >> objections?
> >> >> 
> >> >> in fact, what are everyone's thoughts on doing this on general
> >> >> principle and have a script to then compress ppa entries into one
> >> >> version when/if it gets uploaded to the archive?
> >> >> 
> >> >> right now its an outright mess as one has to check a notes page or
> >> >> ultimately the ppa to find out what ~ppa version is the latest of a
> >> >> given package, having multiple ppas where things could be doesn't
> >> >> really help either.
> >> > 
> >> > Let's see the script that compresses the changelog entries first.  A
> >> > PPA
> >> > upload changelog ought to be uploadable to the archive once the ~ppaX
> >> > is
> >> > removed.
> >> 
> >> Let's make a decision before we have someone waste their life on it,
> >> shall
> >> we?
> > 
> > OK.  Since next workspace is PPA only for some time, I think it's
> > reasonable if there's a script up to when we do the first uploads to the
> > archive, then I think we should do it like other packages where the
> > debian/changelog entries are pre-compacted.
> 
> Mhh, how about putting a metadata file in the relevant branches then?
> The file would always contain the latest version.
> cat _ppa_version
>   4:5.0.1-0kittens11~spaceships100~ppa6
> 
> There's really only those two options IMO. We have to put the data somewhere
> :S

I don't think I'm following you.  What goes in this file that's not already in 
the changelog?

Scott K