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 < [email protected]> 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" <[email protected]> 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
-- Mailing list: https://launchpad.net/~clicompanion-devs Post to : [email protected] Unsubscribe : https://launchpad.net/~clicompanion-devs More help : https://help.launchpad.net/ListHelp
