The push to roundup releases 1.6.1 and 2.0.0alpha1 (and other updates)

"John P. Rouillard" <[email protected]>
Newsgroups gmane.comp.bug-tracking.roundup.devel,gmane.comp.bug-tracking.roundup.user
Message-ID <[email protected]>
Hi Everybody:

It's been about a year since the 1.6.0 release of roundup.

I am going to try to get a new maintenance release for 1.6 out.
Release 1.6.1 will include the following fixes:

  1) CSRF headers now work when using wsgi. (issue2551023)

  2) XSS fix for wsgi and cgi when 404 is generated. (issue2551035)

  3) Install errors for jinja2 and responsive templates fixed. (issue2551029)

  4) doc updates: link rot fixes, config example fixes. 

Does anybody know of other patches that should be backported? Who is
willing to help with testing, documenting or making the changes?

We need a couple more people who can make releases. Anybody
interested in helping get this release out?

There are many new features in the current trunk (which will be the
2.0.0 release). This includes:

  1) roundup is multilingual. It can be used with python 3.4 (or newer)
     or python 2.7.2 or newer. (Note your trackers may need to be
     upgraded to run under python 3 if you are currently using python
     2.  If you are using dbm backends you will have to dump/restore
     the tracker.)

  2) restful interface has been added to roundup. It is in late
     alpha stage. Users and feedback on it are needed to bring it out
     of alpha stage.

  3) login attempts are rate limited to reduce the effectiveness
     of password guessing attacks.

  4) notification messages can be changed by a callback in the
     tracker.

  5) generated links use rel=noopener as well as the existing nofollow.

  6) jinja2 template gets a search page (issue2550901)

  7) all fixes listed above for 1.6.1

  8) postgresql support no longer uses legacy psycopg1 interface which
     was dropped from latest psycopg2 release.

Given the improvements above, I would like to release of 2.0.0alpha1
to pypi. However it should not be the default roundup installed with
"pip install roundup". 

   Does anybody have a foolproof method for doing this? Even better
   Does somebody want to do the release with me?

Before the 2.0.0 production release, we need more people reviewing the
code and using it. You can check out the current head release using:

    hg clone http://hg.code.sf.net/p/roundup/code roundup

and using "python3 ./demo.py" to set up a test instance.

In non-development work, the roundup tracker has a new https url:

   https://issues.roundup-tracker.org/

thanks to the Python Software Foundation.

Also the roundup wiki:

  http://wiki.roundup-tracker.org/

will be moving to a new host. This should provide an https url as
well as better functionality. Hopefully we will see this improvement
in the next couple of months. Thanks to Intevation GmbH for sponsoring
this.

Commits since the last release were done by:

   Chau Nguyen  (Development on 2015 GSOC summer of code, REST interface)
   Ralf Schlatterbeck (Merge/updates for Chau's REST code)
   Joseph Myers (Python 3 support)
   Ezio Melotti
   Bernhard Reiter
   martin.v.loewis
   Gabi Roeger
   Tom Ekberg
   Cédric Krier

For details and attributions on these fixes and huge improvements, see
CHANGES.txt in the roundup distribution or the mercurial timeline:

  https://sourceforge.net/p/roundup/code/ci/tip/log/

--
				-- rouilj
John Rouillard
===========================================================================
My employers don't acknowledge my existence much less my opinions.


_______________________________________________
Roundup-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/roundup-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.