Trac 1.0.3 / 1.1.3

[Ryan Ollos]

I've previously proposed a 2 month release schedule, which suggests Jan 1st for the next set of releases. We've closed 36 tickets for 1.0.3 and 32 tickets for 1.1.3.

I currently have 20 tickets in-progress and would like to close out a few of these; the rest will be moved forward. I propose a code freeze on 1.0-stable and trunk on Jan 1st and I would then create the release by Jan 5th. I'm interested to hear thoughts from other developers on this schedule.

Nothing, to my knowledge, has been done for Trac 0.12.7. The main task we've discussed is to pull the latest translations from Transifex. If nothing is done soon for 0.12.7, then I suggest we just postpone that release but go ahead with 1.0.3 and 1.1.3.

Release ticket for 1.0.3 / 1.1.3: http://trac.edgewall.org/ticket/11827

Next milestones - 1.0.4 and 1.1.4:
http://trac.edgewall.org/milestone/1.0.4

http://trac.edgewall.org/milestone/1.1.4

- Ryan

[Remy Blank]

Ryan Ollos wrote on 2014-12-29 05:03:
> I've previously proposed a 2 month release schedule, which suggests Jan
> 1st for the next set of releases. We've closed 36 tickets for 1.0.3 and
> 32 tickets for 1.1.3.
>
> I currently have 20 tickets in-progress and would like to close out a
> few of these; the rest will be moved forward. I propose a code freeze on
> 1.0-stable and trunk on Jan 1st and I would then create the release by
> Jan 5th. I'm interested to hear thoughts from other developers on this
> schedule.

+1 (from an inactive developer, but interested in seeing the fixes in a
release)

-- Remy

[Peter Suter]

On 29.12.2014 05:03, Ryan Ollos wrote:
> I currently have 20 tickets in-progress and would like to close out a
> few of these; the rest will be moved forward. I propose a code freeze on
> 1.0-stable and trunk on Jan 1st and I would then create the release by
> Jan 5th. I'm interested to hear thoughts from other developers on this
> schedule.

Very good.

I still have three tickets open in 1.1.3:
#11875 (Notification subscriber config section)
#11871 (Notification subscriber for @name mentions) and
#11870 (Optional notification subscribers for watching components,
users, groups, individual resources, ...)

I'll probably move them all to 1.1.4.

It looks like I already created the tracopt/notification folder by
mistake in SVN, which would then remain empty for now. Feel free to
delete it.

http://trac.edgewall.org/ticket/11870
http://trac.edgewall.org/ticket/11871
http://trac.edgewall.org/ticket/11875
http://trac.edgewall.org/browser/trunk/tracopt/notification

--
Peter

[Felix Schwarz]

Am 29.12.2014 um 05:03 schrieb Ryan Ollos:
> I currently have 20 tickets in-progress and would like to close out a few of
> these; the rest will be moved forward. I propose a code freeze on 1.0-stable
> and trunk on Jan 1st and I would then create the release by Jan 5th. I'm
> interested to hear thoughts from other developers on this schedule.

Speaking as a (Fedora) distro packager: I'd welcome regular stable releases
even if they only contain few patches. Usually I don't cherry-pick patches
from SVN so Fedora (mostly) ships pristine Trac tarballs.

If you can release Trac more often this means users get your fixes earlier
(assuming they don't install Trac themself).

Felix

[W. Martin Borgert]

Quoting 'Felix Schwarz' via Trac Development <trac...@googlegroups.com>:
> If you can release Trac more often this means users get your fixes earlier

Adding my 2 cents: I agree with Felix.
It is important, however, that stable releases do not contain many unnessary
changes. E.g. one Trac update had a change of an e-mail address in dozens of
files. This is fine for 1.1 but makes it harder e.g. for Debian to upgrade
the 1.0 line.

Cheers

[Ryan Ollos]

I generally try to push style changes and minimal refactorings to 1.0-stable because it reduces the possibility of merge conflicts later on when merging changes from 1.0-stable to the trunk. However, I'm interested to know how these code changes might make the process for Debian more difficult. What is the process for upgrading the 1.0 package for Debian? I have thought it was nothing more than checking out the release from the repository and creating the package.

[Christian Boos]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

+1 also from me, sorry for the late reply.
I'll move my unfinished tickets to the .4 milestone tomorrow.

- -- Christian

(and happy new year to all ;-) )
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)

iQEcBAEBAgAGBQJUpE04AAoJENf0XkEiCfY2344H/RznD5/bQKjPqbqH4ho9SEAM
OGIuRLJa5OkSkut05kd1RCnNvpEK0KV+DRcz3v6oMpAgfmSs92aTl7fb1pqUhc4n
JUDSmEmvTt1SWLzYAYBOLKjM21V5v32pvKxnG4685C0RIHokUYmUN1GoHDNedbxq
XbxMqTapzysPHMNOR8rxvOlo+0HjS2qRG02zijOlbHTp9M25I7S4wv/uYW82kklZ
mheARYiyaFNd01HfnVZ0+O2kMXiQ2AtHl/QGk02P7e3DOX2EDvNocK5nyFRiXEqG
0x9WKGvPD02f6++pDIJTDcIL2RU0VrF88QOxFLdcqs7bq/Os2GFwkx1JJHfBjiU=
=SBMC
-----END PGP SIGNATURE-----

[RjOllos]

On Wednesday, December 31, 2014 11:23:42 AM UTC-8, cboos wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12/29/2014 10:51 AM, Remy Blank wrote:
> Ryan Ollos wrote on 2014-12-29 05:03:
>> I've previously proposed a 2 month release schedule, which
>> suggests Jan 1st for the next set of releases. We've closed 36
>> tickets for 1.0.3 and 32 tickets for 1.1.3.
>>
>> I currently have 20 tickets in-progress and would like to close
>> out a few of these; the rest will be moved forward. I propose a
>> code freeze on 1.0-stable and trunk on Jan 1st and I would then
>> create the release by Jan 5th. I'm interested to hear thoughts
>> from other developers on this schedule.
>
> +1 (from an inactive developer, but interested in seeing the fixes
> in a release)
>

+1 also from me, sorry for the late reply.
I'll move my unfinished tickets to the .4 milestone tomorrow.

- -- Christian

(and happy new year to all ;-) )

Small update: I'll stop committing changes for existing tickets at end of day Jan 2nd; all of my proposed changes will be posted to tickets by tomorrow. I'll push out the release near end of day on January 6th, which will give time on the 3rd and 4th for reviewing changes, testing and preparing the release.

So if anyone finds time to commit their staged changes before end of day Jan 2nd, please push ahead!

[Steffen Hoffmann]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 31.12.2014 20:23, Christian Boos wrote:
> (and happy new year to all ;-) )

Thank you. If it wasn't said, I would have done so too.

Let's have a good new year with Trac hacking and all the other things
that make life a little better. :-)

Steffen Hoffmann
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlSlHpEACgkQ31DJeiZFuHcJ9QCgku2qGw2goJcY5kWUyKTQRvbO
UVgAoNyp8KbJcYvvjMklBoz53mqhsyYw
=Wv7R
-----END PGP SIGNATURE-----

[RjOllos]

This has taken longer than I'd planned, but it looks like 1.0-stable and trunk are ready for release. I'll wait about a day to see if anyone spots issues, and create the tag tomorrow evening.

I'll try to find time to make the packages tomorrow evening, but that might not happen until Tuesday evening.

[Brettschneider Falk]

Hi,

Ryan, I cannot properly read your emails, since they don’t have the reply indenting (see below). It’s always mixed up with the text you are replying in that moment. Please, check your gmail-settings. Thanks in advance.

CU, F@lk

 

 

Geschäftsführer: Dr. Albert Schmidt · Dr. Oliver Vietze
Sitz der Gesellschaft: Radeberg
Amtsgericht Dresden: HRB 15379
Ust. ID: DE  189714583

 

 

--
You received this message because you are subscribed to the Google Groups "Trac Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to trac-dev+u...@googlegroups.com.
To post to this group, send email to trac...@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

[RjOllos]

On Monday, January 12, 2015 at 12:46:08 AM UTC-8, falkb wrote:

Hi,

Ryan, I cannot properly read your emails, since they don’t have the reply indenting (see below). It’s always mixed up with the text you are replying in that moment. Please, check your gmail-settings. Thanks in advance.

CU, F@lk

I've been posting through the google groups interface, not gmail, so if there is an indentation problem when you receive the emails I doubt there is anything I can do about it.

[Felix Schwarz]

Am 12.01.2015 um 09:55 schrieb RjOllos:
> I've been posting through the google groups interface, not gmail, so if
> there is an indentation problem when you receive the emails I doubt there
> is anything I can do about it.

btw: I can read your emails just fine in Thunderbird.

fs

[RjOllos]

The dist packages are up on the edgewall FTP site now. Each of them needs to be smoke tested, so if anyone has a chance to test one or more of them, please reply here. One issue we've had in the past is the locale data not being distributed with the package. I inspected each of them, but it would be good to confirm that the translations work correctly.

http://download.edgewall.org/trac/Trac-1.0.3.tar.gz
http://download.edgewall.org/trac/Trac-1.0.3.zip
http://download.edgewall.org/trac/Trac-1.0.3.win32.exe
http://download.edgewall.org/trac/Trac-1.0.3.win-amd64.exe
http://download.edgewall.org/trac/Trac-1.1.3.tar.gz
http://download.edgewall.org/trac/Trac-1.1.3.zip
http://download.edgewall.org/trac/Trac-1.1.3.win32.exe
http://download.edgewall.org/trac/Trac-1.1.3.win-amd64.exe

[Christopher Nelson]

On Tue, Jan 13, 2015 at 2:48 AM, RjOllos <rjo...@gmail.com> wrote:
> The dist packages are up on the edgewall FTP site now. ...

Thanks, Ryan.

[RjOllos]

 The 1.0.3 / 1.1.3 release is 16 days later than I had planned, but I'm still hoping to stick to the 2 month release cycle and have the next release out on March 1st. I'll raise a another thread soon to discuss issues around 0.12.7 / 1.0.4 / 1.1.4, and 1.2.

[RjOllos]

On Monday, January 12, 2015 at 12:59:31 AM UTC-8, Felix Schwarz wrote:

I've started to notice things similar to what falkb reported when viewing the message through Mailbox (1) on my mobile device. Most recently this was a case of replying through the Google groups forum page. The quoted message doesn't have a marker so it's indistinguishable from my reply text, and the text of my entire reply is repeated. Maybe the key is to avoid dumb email clients, but if it appears to be only associated with replies through Google groups page, then I'll just start replying directly from email.

(1) http://www.mailboxapp.com/

[RjOllos]

Debian 8 update 6 appears to still have Trac 1.0.2. Will the package be updated anytime soon?

- Ryan 

[Ryan Ollos]

On Sun, Dec 4, 2016 at 3:18 PM W. Martin Borgert <deb...@debian.org> wrote:

On 2016-12-04 13:46, RjOllos wrote:
> Debian 8 update 6 appears to still have Trac 1.0.2. Will the package be
> updated anytime soon?

That is unfortunagely true. I managed to update the package for
Debian unstable on a regular base, but not for stable. I will,
however, try to prepare an official backport to Debian 8 soon.

Thanks. Just for reference, we've been discussing here:

https://groups.google.com/d/msg/trac-users/jOyxkWLcwxQ/gI3m9Ie1BwAJ

- Ryan