openlp-dev team mailing list archive
-
openlp-dev team
-
Mailing list archive
-
Message #00027
Re: Releasing OpenLP 2.2
Hello Raoul, good initiative :)
But... How to subscribe to the new mailing list? :P
--
Daniel Borges Ferreira da Silva
Bacharel em Ciência da computação pela UFAL
Mestrando em Informática pela UFAL
Membro do Núcleo de Excelência em Tecnologias Sociais - NEES
Lattes: <http://lattes.cnpq.br/0755689140229552>http://lattes.cnpq.br/0755689140229552 <http://lattes.cnpq.br/0755689140229552>
> Em 27/08/2015, à(s) 17:02, Raoul Snyman <raoul@xxxxxxxxxxx> escreveu:
>
> Hey guys,
>
> The last few releases we've had have been very impromptu and kinda rushed, and while I'm mostly OK with this for small releases, I don't want this for bigger releases. In fact, even for the smaller releases, it's probably a good idea to stick somewhat to our original game plan.
>
> To recap on our release procedure, this is from the wiki:
>
> Timelines
>
> Feature Freeze: 4 weeks before release
> String Freeze: 2 weeks before release
> Translations Deadline: Thursday before release
> Merge Proposal Freeze: Thursday midnight
> Merge Freeze: Friday noon
> Test Release: Friday midnight
> Source Code Build: Saturday noon
> Package Release: Saturday 18:00 UTC
> Release Announcement: Sunday
>
> Definitions
>
> Feature Freeze:
> No more features can be committed to trunk after this. Any new features will not be merged.
> In addition avoid any code tidies that don't perform any functional benefit.
> E.g. changing variable names, moving modules etc.
>
> String Freeze:
> Developers will cease to make any changes, or add any new strings after this deadline.
>
> Translations Deadline:
> The last date by when translators can submit translations via Transifex or merge proposals.
>
> Merge Proposal Freeze:
> Merges proposed after this date will have to wait for after the release before they can be committed.
>
> Merge Freeze:
> All merge proposals need to be merged by the merge freeze.
>
> Test Release:
> A test release is created, so that the developers can make sure there are no last minute issues.
>
> Source Code Build:
> A final source tarball is created.
>
> Package Release:
> Packages are built and released.
>
> Release Announcement:
> The release announcement is published on the OpenLP site and the download page is updated.
>
>
> With the 2.2 release in particular, I am going to be implementing some architectural changes, and I need everyone to be on board at the release. I still have a lot of work to do with this, and if anyone wants to help out, please let me know.
>
> 1. SSL everywhere.
>
> All the sites will have SSL certificates. Thanks to https://startssl.com/
>
> 2. New website. See http://beta.openlp.org/ - will eventually run on https://openlp.org/
>
> This runs on Nikola, a static site generator, and is exclusively geared to "selling" OpenLP. Comments use Disqus.
>
> lp:openlp/website
>
> 3. Standalone forums. See https://forums.openlp.org/
>
> Forums will become standalone and no longer integrated with the web site. Still need to fix the "mixed content" problem.
>
> 4. Developer central. See https://openlp.io/
>
> This will probably also eventually run Nikola. This is a VPS hosted at Linode.com. Hosts Jenkins, mailing lists and downloads.
>
> 5. New mailing list. Again. Sorry. openlp-dev (at) lists.openlp.io
>
> Launchpad's mailing lists suck. We're moving away from SourceForge.net, and I tried Launchpad.net as a possible solution, but the mailing lists suck and I have no control.
>
> 6. Downloads hosted by Developer Central. https://get.openlp.org/ and https://get.openlp.io/
>
> As mentioned earlier, we're moving away from SF.net, and with this in mind we're going to be moving our downloads to our own server.
>
>
> As always, I'm open to suggestions, comments and criticisms (ouch). 2.2 is going to be a big release, let's get ourselves organised for it.
Follow ups
References