[Trac-dev] Roadmap duedates

On http://trac.edgewall.org/roadmap, each milestone that has a
due-date set is marked as late.

I know that Trac is still being worked on, and I know that the
due-dates have no relationship with when the milestone will be
completed. I'm not complaining, or trying to imply that your not
working fast enough. I know full well that you have no obligation to
do anything on Trac.

I just want to suggest that since the milestone delivery dates aren't
accurate, that they be modified to reflect a new time estimate, or
removed altogether. I'm prompted to suggest this because some people
that I've recommended Trac to have complained that Trac development is
dead, because of the due-date times on the roadmap page.

Cheers

--

-- 
You received this message because you are subscribed to the Google Groups "Trac Development" group.
To post to this group, send email to trac-dev <at> googlegroups.com.
To unsubscribe from this group, send email to trac-dev+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.

Re: [Trac-dev] Roadmap duedates

Michael Jones wrote:
> I just want to suggest that since the milestone delivery dates aren't
> accurate, that they be modified to reflect a new time estimate, or
> removed altogether. I'm prompted to suggest this because some people
> that I've recommended Trac to have complained that Trac development is
> dead, because of the due-date times on the roadmap page.

I tend to agree with that. Removing the due dates altogether has the
disadvantage that the corresponding milestones wouldn't necessarily
appear at the top of the list anymore. But we can certainly adjust the
due dates. I have updated them to reflect reality to some degree.

-- Remy

Re: [Trac-dev] Digest for trac-dev <at> googlegroups.com - 2 Messages in 1 Topic

On 09/12/2011 07:29 PM, trac-dev <at> googlegroups.com wrote:
> But we can certainly adjust the
> due dates. I have updated them to reflect reality to some degree.

Awesome!

Thanks

--

-- 
You received this message because you are subscribed to the Google Groups "Trac Development" group.
To post to this group, send email to trac-dev <at> googlegroups.com.
To unsubscribe from this group, send email to trac-dev+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.

[Trac-dev] Trac Ticketing System.

Re: [Trac-dev] Trac Ticketing System.

2011/9/13 A, Thiyagarajan (NSN - IN/Bangalore) <thiyagarajan.a <at> nsn.com>:
> Hi,
>
> I just want to customize my Trac Application. Whenever any tickets are
> created, I want to keep some criteria like some particular fields are not
> filed it should not allow users to create ticket. So can you please help me
> on this.
>

Here is a plugin that may do what you need. Take a look.

https://github.com/daltonmatos/trac-plugins/tree/master/ConditionalFieldsPlugin

-- 
Dalton Barreto
http://daltonmatos.com

--

-- 
You received this message because you are subscribed to the Google Groups "Trac Development" group.
To post to this group, send email to trac-dev <at> googlegroups.com.
To unsubscribe from this group, send email to trac-dev+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.

Re: [Trac-dev] Roadmap duedates

On 9/12/2011 10:11 PM, Remy Blank wrote:
> Michael Jones wrote:
>> I just want to suggest that since the milestone delivery dates aren't
>> accurate, that they be modified to reflect a new time estimate, or
>> removed altogether. I'm prompted to suggest this because some people
>> that I've recommended Trac to have complained that Trac development is
>> dead, because of the due-date times on the roadmap page.
>
> I tend to agree with that. Removing the due dates altogether has the
> disadvantage that the corresponding milestones wouldn't necessarily
> appear at the top of the list anymore. But we can certainly adjust the
> due dates. I have updated them to reflect reality to some degree.
>

But then, how will we be able to say "oops, we're X years late" accurately?

 More seriously, we should try to get the ball rolling once again 
with the releases, we have some good stuff pending in both the stable 
and development branches.

I've updated previously TracDev/ToDo to reflect that, my estimation was 
somehow more optimistic than Remy's (0.12.3 by end of this month and 
0.13 by end of this year). We'll see 

-- Christian

--

-- 
You received this message because you are subscribed to the Google Groups "Trac Development" group.
To post to this group, send email to trac-dev <at> googlegroups.com.
To unsubscribe from this group, send email to trac-dev+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.

RE: [Trac-dev] Trac Ticketing System.

I have field TYPE where we have this many options " ---select type---,
defect, enchancement,task , question". So by default it wil be "
---select type--- ". When ticket is created it shd check if the ticket
type is default then tickets should not create it should prompt user to
select the type.  

-----Original Message-----
From: trac-dev <at> googlegroups.com [mailto:trac-dev <at> googlegroups.com] On
Behalf Of ext Dalton Barreto
Sent: Tuesday, September 13, 2011 7:02 PM
To: trac-dev <at> googlegroups.com
Subject: Re: [Trac-dev] Trac Ticketing System.

2011/9/13 A, Thiyagarajan (NSN - IN/Bangalore) <thiyagarajan.a <at> nsn.com>:
> Hi,
>
> I just want to customize my Trac Application. Whenever any tickets are
> created, I want to keep some criteria like some particular fields are
not
> filed it should not allow users to create ticket. So can you please
help me
> on this.
>

Here is a plugin that may do what you need. Take a look.

https://github.com/daltonmatos/trac-plugins/tree/master/ConditionalField
sPlugin

-- 
Dalton Barreto
http://daltonmatos.com

-- 
You received this message because you are subscribed to the Google
Groups "Trac Development" group.
To post to this group, send email to trac-dev <at> googlegroups.com.
To unsubscribe from this group, send email to
trac-dev+unsubscribe <at> googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/trac-dev?hl=en.

--

-- 
You received this message because you are subscribed to the Google Groups "Trac Development" group.
To post to this group, send email to trac-dev <at> googlegroups.com.
To unsubscribe from this group, send email to trac-dev+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.

[Trac-dev] Preparing 0.12.3

Hello all,
	
As already discussed recently, it would be a good thing to release 
0.12.3 "soon", if only to show that we're still alive. The other 
benefits include making available a few fixes for bugs that people keep 
hitting with 0.12.2 and last but not least it will be a good opportunity 
for getting our new team members involved in the tedious but oh-so much 
gratifying task of making a release  (yes, Jun and Peter I'm talking 
about you  ).

So the plan is the following:
  - look at the tickets remaining on the 0.12.3 milestone
  - people not yet familiar with the release process could check 
TracDev/ReleaseChecklist, try to produce the packages on their own and 
do some testing for various configurations, DB back-ends and web front-ends
  - next week we should find a moment when we could gather on #trac to 
triage the 0.12.3 tickets, eventually finish some of them together and 
at least know precisely what we want to have done for that version
  - we'll also see at this occasion if we can enter the string freeze 
and if so, notify our translators

As this is merely a routine release without much pressure, it will 
really be a good occasion for me and Remy to show the others how they 
can make a Trac release!

And after that, full steam on 0.13 

-- Christian

--

-- 
You received this message because you are subscribed to the Google Groups "Trac Development" group.
To post to this group, send email to trac-dev <at> googlegroups.com.
To unsubscribe from this group, send email to trac-dev+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.

Re: [Trac-dev] Trac Ticketing System.

Am 14.09.2011 08:05, schrieb A, Thiyagarajan (NSN - IN/Bangalore):
> Here is a plugin that may do what you need. Take a look.
> 
> https://github.com/daltonmatos/trac-plugins/tree/master/ConditionalField
> sPlugin

ConditionalFields should do fine, but I've not used it by now. Did you
succeed already?

If not, you might want to have a look at DynamicFieldsPlugin. With your
requirement in mind I would setup

[ticket-custom]
summary.clear_on_hide = true
summary.hide_when_type = '---select type---'

Untested, but you'll get the idea. I've chosen summary, because without
summary Trac will complain and deny to create the ticket, so you should
get exactly what you want. Still required field coloring might be a nice
(unique) feature of ConditionalFields.

Would be nice, if you'd report back on success too. Thanks.

Steffen Hoffmann
(hasienda)

[1] http://trac-hacks.org/wiki/DynamicFieldsPlugin

[Trac-dev] Trac plugin translations <at> Transifex

If you're not involved with this work, just disregard the following, please.

Dear fellow developers and translators.

I remember a thread at this list regarding "if and how should
translators for Trac be give credits for their work" before the 0.12
release. Meanwhile I've promoted translation effort for Trac plugins [1]
bundling message catalogs for easier access.

Guess what? This has not caused a rush to push translations to get level
with Trac so far, despite me being quite careful to give credit for any
contribution. I advocate for a policy to do so in Trac too. Regarding my
own (non-software centric) Trac applications a fully localized web-UI
has always been crucial for general acceptance and success. I see no
reason, why I should be the only one seeing this.

As I see it for spreading the word about Trac we need translations and
the people teaming, discussing, struggling to contributing them - we
need them badly. Knowing, there's still a good amount of time before
Trac 0.13, I'd like to hear other opinions on the subject.

Sincerely,

Steffen Hoffmann
(hasienda)

[1] http://trac-hacks.org/wiki/TracPluginTranslation