clicompanion-devs team mailing list archive

[David Caro Estévez <david.caro.estevez@xxxxxxxxx>]

I've been loking, and our nightlies ppa (the only one that we have, I
think), has the upated code (the trunk). Uploaded by Jonathan, 10 hours ago
(only the last commit is missing, but I supose that tonight it will be
added).

If what you mean is making another ppa with a stable version, we still nedd
this (extracted from the release plan for 1.0 series):
* Fix bugs from last public release before 1.0 stable: #TODO -- what I've
been doing
* Review and possibly expand the default command list (small) #IN PROGRESS
* We need File, Edit, Help menus across the top, #IN PROGRESS
         EDIT: Help works, About still does not. SEE
https://bugs.launchpad.net/clicompanion/+bug/643125 #TODO
* l18n (medium)
https://blueprints.launchpad.net/clicompanion/+spec/add-internationalization#DONE
    EDIT: Some work needs to be done making sure all the strings in the app
are being translated. See:
https://bugs.launchpad.net/clicompanion/+bug/682841



Also some of the bugs are not related to a patch or a branch, so I'm unable
to decide if they are ready to be marked as released or not:
lp:648963
lp:643125
lp:612622


So please, try to update the status of those bugs (preferably link them to
a patch or a branch so the changes introduced are traceable).
Meanwhile, I'm trying to fix the bugs that I can.

We should try to document in every bug the code that was changed (a patch
or a branch, a branch should be easily traceable).


On Sat, Dec 31, 2011 at 2:27 AM, Matthew Byers <faintstlsaint@xxxxxxxxx>wrote:

> Im sure jmarsden can explain in more proper terms but the way i understand
> it is:
>
> 1. Tarball the source
> 2. Create a signed deb and upload it unto launchpad. (Launchpad has a
> explanation of how to make a release through them.)
>
> Thats it for a basic release as im tracking.
>
>
> On Fri, Dec 30, 2011 at 6:46 PM, David Caro Estévez <
> david.caro.estevez@xxxxxxxxx> wrote:
>
>> Ok, I agree on making a release.
>> Tomorrow I will take a look at how releases are done (and how we make
>> them). But I'd really appreciate if you explain it a little how we do it
>> with your own words (or someone else that knows how it's done), to have
>> something to start from.
>>
>> Thanks,
>> David
>> El 31/12/2011 01:03, "Matthew Byers" <faintstlsaint@xxxxxxxxx> escribió:
>>
>> I see alot of new work (bugs/patches) coming abotu David and your work is
>>> greatly appreciated and needed but we need to save these additions for next
>>> release. We keep adding patches when really we need to release and add the
>>> new fixes into our ppa for nightlys. We keep halting work and pushing back
>>> a release. There is no VALID reason that we have not released yet. NOT ONE!
>>> If there is more bugs users find that is great and that is what we can use
>>> the ppa and save for another release but right now we have extremely old
>>> code in our site and that is what users are stuck with downloading. We can
>>> still continue works toward pushing upstream but here and now why are we
>>> not releasing???
>>>
>>> --
>>> God Bless
>>>
>>
>
>
> --
> God Bless
>