Re: [Twisted-Python] Attaching the release number to a closed/merged ticket

2015-12-07 Thread Tom Prince
> Amber commented that using milestones for such a thing is not a good idea > and that we should use tags like: landed-in-15.5, landed-for-15.5 ... and > keep milestones like Python-3 unchanged. I think rather than having a tag, it would make more sense to have a custom field

Re: [Twisted-Python] Attaching the release number to a closed/merged ticket

2015-12-07 Thread Adi Roiban
On 5 December 2015 at 19:31, Tom Prince wrote: > > Amber commented that using milestones for such a thing is not a good idea > > and that we should use tags like: landed-in-15.5, landed-for-15.5 ... and > > keep milestones like Python-3 unchanged. > > I think rather than

Re: [Twisted-Python] Attaching the release number to a closed/merged ticket

2015-12-07 Thread Tom Prince
Glyph Lefkowitz writes: > I frequently answer stack overflow questions where I want to say what release > of Twisted a particular bug was fixed in, and it's unfortunately hard to > discover. The attached script should get most of the versions for tickets. There are a

Re: [Twisted-Python] Attaching the release number to a closed/merged ticket

2015-12-06 Thread Adi Roiban
On 5 December 2015 at 02:17, Glyph Lefkowitz wrote: > > > On Dec 4, 2015, at 4:51 AM, Adi Roiban wrote: > > > > Hi, > > > > Please send your suggestions and comments. > > By "tags" do you mean "keywords"? If so, couldn't we just use the >

Re: [Twisted-Python] Attaching the release number to a closed/merged ticket

2015-12-06 Thread Glyph Lefkowitz
> On Dec 6, 2015, at 8:04 AM, Adi Roiban wrote: > > > > On 5 December 2015 at 02:17, Glyph Lefkowitz > wrote: > > > On Dec 4, 2015, at 4:51 AM, Adi Roiban > > wrote: > > > >

[Twisted-Python] Attaching the release number to a closed/merged ticket

2015-12-04 Thread Adi Roiban
Hi, I would like to ask you if you think that is a good idea to have the version of Twisted in which the changes associated with a ticket. The use case would be: Someone search the net for something related to Twisted (a bug or some feature) and the land to a Trac ticket. Just by looking at the

Re: [Twisted-Python] Attaching the release number to a closed/merged ticket

2015-12-04 Thread Glyph Lefkowitz
> On Dec 4, 2015, at 4:51 AM, Adi Roiban wrote: > > Hi, > > I would like to ask you if you think that is a good idea to have the version > of Twisted in which the changes associated with a ticket. > > The use case would be: Someone search the net for something related to >