Edgewall Software
Modify

Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#12588 closed task (fixed)

Release Trac 1.3.1

Reported by: Ryan J Ollos Owned by: Christian Boos
Priority: normal Milestone: 1.3.1
Component: general Version:
Severity: normal Keywords: release
Cc: Branch:
Release Notes:
API Changes:
Internal Changes:

Description

This ticket is used to coordinate the finalization and testing of the next development-stable release of Trac, 1.3.1.

Attachments (0)

Change History (8)

comment:1 by Christian Boos, 4 years ago

I'd propose to release 1.3.1 "as is", in the same time frame as 1.2. That would provide a good basis for people wanting to use a "modernized" 1.2 for Python 2.7, with no legacy code (#11901), yet without any of the more "drastic" changes to come (#12130, Jinja2 templates).

Last edited 4 years ago by Christian Boos (previous) (diff)

comment:2 by Ryan J Ollos, 4 years ago

I'm hoping to release 1.2 next week, provided no significant issues are raised with rc1. The release takes less than 2 hours to create, so I could release 1.3.1 when the Jinja2 work is ready to be merged into trunk. I've put a due date of Nov 6th for 1.3.1 in the milestone, but no problem if it's sooner than that.

comment:3 by Christian Boos, 4 years ago

Owner: set to Christian Boos
Status: newassigned

I've uploaded the 1.3.1rc1 packages just now (TracDownload@189#LatestDevRelease). Please give me some feedback, it's been a while and I may have forgotten something… If everything is fine, I'll continue with the real 1.3.1.

comment:4 by Ryan J Ollos, 4 years ago

The packages look good to me. I tested the whl, tar.gz and zip on OSX.

comment:5 by Christian Boos, 4 years ago

Resolution: fixed
Status: assignedclosed

Thanks for testing.

I just repackaged the 1.3.1 release at the same revision r15269, without the rc1 tag and with some changes to the TracChangeLog page (see r15278).

So the latest changes from trunk [15269:15277] are not in 1.3.1, because I wanted to stay consistent with the .rc and didn't want to re-test everything. No worries, 1.3.2 should come soon ;-)

comment:6 by Ryan J Ollos, 4 years ago

r15277 looks very useful! I will use the new make commands today while working on #12578.

make release-env could be useful for creating a virtual environment with the dependencies (TracDev/ReleaseChecklist#Prerequisites).

I always do these steps:

$ virtualenv pve-release
$ . pve-release/bin/activate
$ pip install -U setuptools pip wheel virtualenv
$ pip install setuptools-svn setuptools-subversion babel genshi

comment:7 by Jun Omae, 4 years ago

After [15280], clean target is unable to work.

$ make clean
find . -name \*.py[co] -exec rm {} \;
make: *** No rule to make target `clean-figleaf', needed by `clean'.  Stop.

in reply to:  7 comment:8 by Christian Boos, 4 years ago

Replying to Jun Omae:

After [15280], clean target is unable to work.

Oops, thanks for the heads-up! Fixed in r15284 and merged up.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain Christian Boos.
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from Christian Boos to the specified user.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.