Trac -> Jira

On 5/17/11 10:32 PM, Lukas Rytz wrote:
> our plan is to migrate from trac to Jira this afternoon
> .
> For some time, trac will be
> read-only and Jira not yet available.
>
> Let us know if you have any considerations.

Can we make super sure to get a clean backup of trac?

(And send me a copy?)

Sure. I can send you a copy as well.
We will probably let it run for some time in read-only. However, this might be on a differentaddress since for the current ticket URLs we'll put forwarders to Jira.
Lukas

On Wed, May 18, 2011 at 07:46, Paul Phillips <paulp@improving.org> wrote:

On 5/17/11 10:32 PM, Lukas Rytz wrote:
> our plan is to migrate from trac to Jira this afternoon
> <http://www.timeanddate.com/worldclock/fixedtime.html?iso=20110518T14&p1=270>.
> For some time, trac will be
> read-only and Jira not yet available.
>
> Let us know if you have any considerations.

Can we make super sure to get a clean backup of trac?

(And send me a copy?)

That's fantastic news!
Will we also have Jira/Fisheye/Crucible set up to support connections via mylyn et. al?

On 18 May 2011 06:56, Lukas Rytz <lukas.rytz@epfl.ch> wrote:

Sure. I can send you a copy as well.
We will probably let it run for some time in read-only. However, this might be on a different address since for the current ticket URLs we'll put forwarders to Jira.
Lukas

On Wed, May 18, 2011 at 07:46, Paul Phillips <paulp@improving.org> wrote:

On 5/17/11 10:32 PM, Lukas Rytz wrote:
> our plan is to migrate from trac to Jira this afternoon
> <http://www.timeanddate.com/worldclock/fixedtime.html?iso=20110518T14&p1=270>.
> For some time, trac will be
> read-only and Jira not yet available.
>
> Let us know if you have any considerations.

Can we make super sure to get a clean backup of trac?

(And send me a copy?)

--
Kevin Wright

gtalk / msn : kev.lee.wright@gmail.comkev.lee.wright@gmail.commail: kevin.wright@scalatechnology.com
vibe / skype: kev.lee.wrightquora: http://www.quora.com/Kevin-Wright
twitter: @thecoda

"My point today is that, if we wish to count lines of code, we should not regard them as "lines produced" but as "lines spent": the current conventional wisdom is so foolish as to book that count on the wrong side of the ledger" ~ Dijkstra

sure, no reason not to i guess. let's get the basic thing running first and thenwe can see what needs to be added.

On Wed, May 18, 2011 at 10:02, Kevin Wright <kev.lee.wright@gmail.com> wrote:

That's fantastic news!
Will we also have Jira/Fisheye/Crucible set up to support connections via mylyn et. al?

On 18 May 2011 06:56, Lukas Rytz <lukas.rytz@epfl.ch> wrote:

Sure. I can send you a copy as well.
We will probably let it run for some time in read-only. However, this might be on a different address since for the current ticket URLs we'll put forwarders to Jira.
Lukas

On Wed, May 18, 2011 at 07:46, Paul Phillips <paulp@improving.org> wrote:

On 5/17/11 10:32 PM, Lukas Rytz wrote:
> our plan is to migrate from trac to Jira this afternoon
> <http://www.timeanddate.com/worldclock/fixedtime.html?iso=20110518T14&p1=270>.
> For some time, trac will be
> read-only and Jira not yet available.
>
> Let us know if you have any considerations.

Can we make super sure to get a clean backup of trac?

(And send me a copy?)

--
Kevin Wright

gtalk / msn : kev.lee.wright@gmail.comkev.lee.wright@gmail.commail: kevin.wright@scalatechnology.com
vibe / skype: kev.lee.wrightquora: http://www.quora.com/Kevin-Wright
twitter: @thecoda

"My point today is that, if we wish to count lines of code, we should not regard them as "lines produced" but as "lines spent": the current conventional wisdom is so foolish as to book that count on the wrong side of the ledger" ~ Dijkstra

There's some rather nice Android/iOS apps available for talking to Jira if you do :)
I use the Trac RSS feed via Google Reader at the moment, but it's not exactly the best UI going for this sort of thing.


On 18 May 2011 09:07, Lukas Rytz <lukas.rytz@epfl.ch> wrote:

sure, no reason not to i guess. let's get the basic thing running first and thenwe can see what needs to be added.

On Wed, May 18, 2011 at 10:02, Kevin Wright <kev.lee.wright@gmail.com> wrote:

That's fantastic news!
Will we also have Jira/Fisheye/Crucible set up to support connections via mylyn et. al?

On 18 May 2011 06:56, Lukas Rytz <lukas.rytz@epfl.ch> wrote:

Sure. I can send you a copy as well.
We will probably let it run for some time in read-only. However, this might be on a different address since for the current ticket URLs we'll put forwarders to Jira.
Lukas

On Wed, May 18, 2011 at 07:46, Paul Phillips <paulp@improving.org> wrote:

On 5/17/11 10:32 PM, Lukas Rytz wrote:
> our plan is to migrate from trac to Jira this afternoon
> <http://www.timeanddate.com/worldclock/fixedtime.html?iso=20110518T14&p1=270>.
> For some time, trac will be
> read-only and Jira not yet available.
>
> Let us know if you have any considerations.

Can we make super sure to get a clean backup of trac?

(And send me a copy?)

--
Kevin Wright

gtalk / msn : kev.lee.wright@gmail.comkev.lee.wright@gmail.commail: kevin.wright@scalatechnology.com
vibe / skype: kev.lee.wrightquora: http://www.quora.com/Kevin-Wright
twitter: @thecoda

"My point today is that, if we wish to count lines of code, we should not regard them as "lines produced" but as "lines spent": the current conventional wisdom is so foolish as to book that count on the wrong side of the ledger" ~ Dijkstra

--
Kevin Wright

gtalk / msn : kev.lee.wright@gmail.comkev.lee.wright@gmail.commail: kevin.wright@scalatechnology.com
vibe / skype: kev.lee.wrightquora: http://www.quora.com/Kevin-Wright
twitter: @thecoda

"My point today is that, if we wish to count lines of code, we should not regard them as "lines produced" but as "lines spent": the current conventional wisdom is so foolish as to book that count on the wrong side of the ledger" ~ Dijkstra

I'm rather fond of my Trac RSS feed through Google Reader, actually.
Does JIRA has something like that?

On Wed, May 18, 2011 at 05:12, Kevin Wright wrote:
> There's some rather nice Android/iOS apps available for talking to Jira if
> you do :)
> I use the Trac RSS feed via Google Reader at the moment, but it's not
> exactly the best UI going for this sort of thing.
>
>
> On 18 May 2011 09:07, Lukas Rytz wrote:
>>
>> sure, no reason not to i guess. let's get the basic thing running first
>> and then
>> we can see what needs to be added.
>>
>> On Wed, May 18, 2011 at 10:02, Kevin Wright
>> wrote:
>>>
>>> That's fantastic news!
>>> Will we also have Jira/Fisheye/Crucible set up to support connections via
>>> mylyn et. al?
>>>
>>> On 18 May 2011 06:56, Lukas Rytz wrote:
>>>>
>>>> Sure. I can send you a copy as well.
>>>> We will probably let it run for some time in read-only. However, this
>>>> might be on a different
>>>> address since for the current ticket URLs we'll put forwarders to Jira.
>>>> Lukas
>>>>
>>>> On Wed, May 18, 2011 at 07:46, Paul Phillips
>>>> wrote:
>>>>>
>>>>> On 5/17/11 10:32 PM, Lukas Rytz wrote:
>>>>> > our plan is to migrate from trac to Jira this afternoon
>>>>> >
>>>>> > .
>>>>> > For some time, trac will be
>>>>> > read-only and Jira not yet available.
>>>>> >
>>>>> > Let us know if you have any considerations.
>>>>>
>>>>> Can we make super sure to get a clean backup of trac?
>>>>>
>>>>> (And send me a copy?)
>>>>
>>>
>>>
>>>
>>> --
>>> Kevin Wright
>>>
>>> gtalk / msn : kev.lee.wright@gmail.com
>>> mail: kevin.wright@scalatechnology.com
>>> vibe / skype: kev.lee.wright
>>> quora: http://www.quora.com/Kevin-Wright
>>> twitter: @thecoda
>>>
>>> "My point today is that, if we wish to count lines of code, we should not
>>> regard them as "lines produced" but as "lines spent": the current
>>> conventional wisdom is so foolish as to book that count on the wrong side of
>>> the ledger" ~ Dijkstra
>>
>
>
>
> --
> Kevin Wright
>
> gtalk / msn : kev.lee.wright@gmail.com
> mail: kevin.wright@scalatechnology.com
> vibe / skype: kev.lee.wright
> quora: http://www.quora.com/Kevin-Wright
> twitter: @thecoda
>
> "My point today is that, if we wish to count lines of code, we should not
> regard them as "lines produced" but as "lines spent": the current
> conventional wisdom is so foolish as to book that count on the wrong side of
> the ledger" ~ Dijkstra
>

Sure, Jira has RSS feeds.  You can even create your own based on some filter.(I'm sure a filter showing only Paul's commit messages would be immensely popular)
I'd point you to a link, but the thing is currently hanging when I try to log in.


On 18 May 2011 15:01, Daniel Sobral <dcsobral@gmail.com> wrote:

I'm rather fond of my Trac RSS feed through Google Reader, actually.
Does JIRA has something like that?

On Wed, May 18, 2011 at 05:12, Kevin Wright <kev.lee.wright@gmail.com> wrote:
> There's some rather nice Android/iOS apps available for talking to Jira if
> you do :)
> I use the Trac RSS feed via Google Reader at the moment, but it's not
> exactly the best UI going for this sort of thing.
>
>
> On 18 May 2011 09:07, Lukas Rytz <lukas.rytz@epfl.ch> wrote:
>>
>> sure, no reason not to i guess. let's get the basic thing running first
>> and then
>> we can see what needs to be added.
>>
>> On Wed, May 18, 2011 at 10:02, Kevin Wright <kev.lee.wright@gmail.com>
>> wrote:
>>>
>>> That's fantastic news!
>>> Will we also have Jira/Fisheye/Crucible set up to support connections via
>>> mylyn et. al?
>>>
>>> On 18 May 2011 06:56, Lukas Rytz <lukas.rytz@epfl.ch> wrote:
>>>>
>>>> Sure. I can send you a copy as well.
>>>> We will probably let it run for some time in read-only. However, this
>>>> might be on a different
>>>> address since for the current ticket URLs we'll put forwarders to Jira.
>>>> Lukas
>>>>
>>>> On Wed, May 18, 2011 at 07:46, Paul Phillips <paulp@improving.org>
>>>> wrote:
>>>>>
>>>>> On 5/17/11 10:32 PM, Lukas Rytz wrote:
>>>>> > our plan is to migrate from trac to Jira this afternoon
>>>>> >
>>>>> > <http://www.timeanddate.com/worldclock/fixedtime.html?iso=20110518T14&p1=270>.
>>>>> > For some time, trac will be
>>>>> > read-only and Jira not yet available.
>>>>> >
>>>>> > Let us know if you have any considerations.
>>>>>
>>>>> Can we make super sure to get a clean backup of trac?
>>>>>
>>>>> (And send me a copy?)
>>>>
>>>
>>>
>>>
>>> --
>>> Kevin Wright
>>>
>>> gtalk / msn : kev.lee.wright@gmail.com
>>> mail: kevin.wright@scalatechnology.com
>>> vibe / skype: kev.lee.wright
>>> quora: http://www.quora.com/Kevin-Wright
>>> twitter: @thecoda
>>>
>>> "My point today is that, if we wish to count lines of code, we should not
>>> regard them as "lines produced" but as "lines spent": the current
>>> conventional wisdom is so foolish as to book that count on the wrong side of
>>> the ledger" ~ Dijkstra
>>
>
>
>
> --
> Kevin Wright
>
> gtalk / msn : kev.lee.wright@gmail.com
> mail: kevin.wright@scalatechnology.com
> vibe / skype: kev.lee.wright
> quora: http://www.quora.com/Kevin-Wright
> twitter: @thecoda
>
> "My point today is that, if we wish to count lines of code, we should not
> regard them as "lines produced" but as "lines spent": the current
> conventional wisdom is so foolish as to book that count on the wrong side of
> the ledger" ~ Dijkstra
>



--
Daniel C. Sobral

I travel to the future all the time.

--
Kevin Wright

gtalk / msn : kev.lee.wright@gmail.comkev.lee.wright@gmail.commail: kevin.wright@scalatechnology.com
vibe / skype: kev.lee.wrightquora: http://www.quora.com/Kevin-Wright
twitter: @thecoda

"My point today is that, if we wish to count lines of code, we should not regard them as "lines produced" but as "lines spent": the current conventional wisdom is so foolish as to book that count on the wrong side of the ledger" ~ Dijkstra

The migration is completed.
You can access the new bugtracker on https://issues.scala-lang.org
Existing ticket numbers are the same as before. We will install redirections from old-ticket-URL's to the new ones.
The user accounts have been migrated as well, the passwords are the same.
Lukas

On Wed, May 18, 2011 at 07:32, Lukas Rytz <lukas.rytz@epfl.ch> wrote:

Hi all,
our plan is to migrate from trac to Jira this afternoon. For some time, trac will be read-only and Jira not yet available.
Let us know if you have any considerations.
Lukas

The old trac is now here:

On 05/18/2011 05:43 PM, Lukas Rytz wrote:
> The migration is completed.
>
> You can access the new bugtracker on https://issues.scala-lang.org
>
> Existing ticket numbers are the same as before.
> We will install redirections from old-ticket-URL's to the new ones.
>
> The user accounts have been migrated as well, the passwords are the same.
>
> Lukas
>
>
> On Wed, May 18, 2011 at 07:32, Lukas Rytz > wrote:
>
> Hi all,
>
> our plan is to migrate from trac to Jira this afternoon
> .
> For some time, trac will be
> read-only and Jira not yet available.
>
> Let us know if you have any considerations.

--
Fabien Salvi

On Wed, May 18, 2011 at 18:29, Fabien Salvi <fabien.salvi@epfl.ch> wrote:

The old trac is now here:
<https://lampsvn.epfl.ch/trac/scala-old/>

On 05/18/2011 05:43 PM, Lukas Rytz wrote:

The migration is completed.

You can access the new bugtracker on https://issues.scala-lang.org

Existing ticket numbers are the same as before.
We will install redirections from old-ticket-URL's to the new ones.

The user accounts have been migrated as well, the passwords are the same.

Actually, all usernames were converted to lowercase! 

Lukas


On Wed, May 18, 2011 at 07:32, Lukas Rytz <lukas.rytz@epfl.ch
<mailto:lukas.rytz@epfl.ch>> wrote:

   Hi all,

   our plan is to migrate from trac to Jira this afternoon
   <http://www.timeanddate.com/worldclock/fixedtime.html?iso=20110518T14&p1=270>.
   For some time, trac will be
   read-only and Jira not yet available.

   Let us know if you have any considerations.

--
Fabien Salvi

On 5/18/11 9:40 AM, Lukas Rytz wrote:
> Actually, all *usernames were converted to lowercase*!

Ha ha, upper case people! I think that's a feature.

Can we please get forwarders on https as well as http (they are
presently broken.) Almost all my bookmarks are https, and since I didn't
go out of my way for that, I assume it is true of most people. Example
of not working:

https://lampsvn.epfl.ch/trac/scala/ticket/4500

On Wed, May 18, 2011 at 12:43, Lukas Rytz wrote:
> The migration is completed.
> You can access the new bugtracker on https://issues.scala-lang.org
> Existing ticket numbers are the same as before.
> We will install redirections from old-ticket-URL's to the new ones.
> The user accounts have been migrated as well, the passwords are the same.
> Lukas

Now we have to get someone to point scalabot to JIRA. :-)

This is cool: thank you Lukas and Fabien.
However, I don't know anymore where to find the wiki pages that were managed by Trac, such as the Scaladoc minisite. Have you moved them to a new place?
Cheers,Gilles.

On Wednesday, May 18, 2011, Gilles Dubochet wrote:
> This is cool: thank you Lukas and Fabien.
> However, I don't know anymore where to find the wiki pages that were managed by Trac, such as the Scaladoc minisite. Have you moved them to a new place?

not yet. i will move them to wiki.scala-lang.org soon.
in the meantime they're available on the link that fabien sent.

> Cheers,Gilles.
>

Confluence too?  This just keeps on giving...

On 18 May 2011 18:20, Lukas Rytz <lukas.rytz@epfl.ch> wrote:

On Wednesday, May 18, 2011, Gilles Dubochet <gilles.dubochet@epfl.ch> wrote:
> This is cool: thank you Lukas and Fabien.
> However, I don't know anymore where to find the wiki pages that were managed by Trac, such as the Scaladoc minisite. Have you moved them to a new place?

not yet. i will move them to wiki.scala-lang.org soon.
in the meantime they're available on the link that fabien sent.

> Cheers,Gilles.
>

--
Kevin Wright

gtalk / msn : kev.lee.wright@gmail.comkev.lee.wright@gmail.commail: kevin.wright@scalatechnology.com
vibe / skype: kev.lee.wrightquora: http://www.quora.com/Kevin-Wright
twitter: @thecoda

"My point today is that, if we wish to count lines of code, we should not regard them as "lines produced" but as "lines spent": the current conventional wisdom is so foolish as to book that count on the wrong side of the ledger" ~ Dijkstra

The forwarders are necessary asap. Right now there is a considerable
amount of breakage resulting from the migration:

- all existing links to tickets are broken, but also
- source links from all existing Scala APIs are similarly broken
- the Scala Version page is no longer functional (this may not be
recoverable any time soon; we may end up removing it altogether):
http://www.scala-lang.org/node/299

On 18/05/2011 19:32, Kevin Wright wrote:
> Confluence too? This just keeps on giving...
>
> On 18 May 2011 18:20, Lukas Rytz > wrote:
>
> On Wednesday, May 18, 2011, Gilles Dubochet > wrote:
> > This is cool: thank you Lukas and Fabien.
> > However, I don't know anymore where to find the wiki pages that
> were managed by Trac, such as the Scaladoc minisite. Have you moved
> them to a new place?
>
> not yet. i will move them to wiki.scala-lang.org
> soon.
> in the meantime they're available on the link that fabien sent.
>
> > Cheers,Gilles.
> >
>
>
>
>
> --
> Kevin Wright
>
> gtalk / msn : kev.lee.wright@gmail.com
> mail: kevin.wright@scalatechnology.com
>
> vibe / skype: kev.lee.wright
> quora: http://www.quora.com/Kevin-Wright
> twitter: @thecoda
>
> "My point today is that, if we wish to count lines of code, we should
> not regard them as "lines produced" but as "lines spent": the current
> conventional wisdom is so foolish as to book that count on the wrong
> side of the ledger" ~ Dijkstra
>

> Can we please get forwarders on https as well as http

And for source code as well, please. All the source links in Scaladoc
are right now broken even with http because there's a double slash
somewhere in the path.

Ok, done.

On 05/18/2011 06:55 PM, Paul Phillips wrote:
> On 5/18/11 9:40 AM, Lukas Rytz wrote:
>> Actually, all *usernames were converted to lowercase*!
>
> Ha ha, upper case people! I think that's a feature.
>
> Can we please get forwarders on https as well as http (they are
> presently broken.) Almost all my bookmarks are https, and since I didn't
> go out of my way for that, I assume it is true of most people. Example
> of not working:
>
> https://lampsvn.epfl.ch/trac/scala/ticket/4500

--
Fabien Salvi

On 05/18/2011 07:15 PM, Gilles Dubochet wrote:
> This is cool: thank you Lukas and Fabien.
>
> However, I don't know anymore where to find the wiki pages that were
> managed by Trac, such as the Scaladoc minisite. Have you moved them to a
> new place?

For the moment, you can access them on the old trac:
http://lampsvn.epfl.ch/trac/scala-old/wiki/Scaladoc

We are setting up the wiki part (confluence), so wiki pages will be
imported soon I guess.

--
Fabien Salvi

Well, the problem is in scaladoc itself (eg link
)
The // wasn't a problem with Trac, but fisheye doesn't like it.

For the moment, I enabled again the browse source on the old URL and
removed the redirection.
I will try to find a better solution.

On 05/18/2011 08:21 PM, Johannes Rudolph wrote:
>> Can we please get forwarders on https as well as http
>
> And for source code as well, please. All the source links in Scaladoc
> are right now broken even with http because there's a double slash
> somewhere in the path.

--
Fabien Salvi

One thing that would be good to have is filter the list of possible assignees to Scala committers. It's quite hard to go through the list of everyone who's registered when you want top assign a ticket to someone.

Cheers

 -- Martin


On Thu, May 19, 2011 at 10:28 AM, Fabien Salvi <fabien.salvi@epfl.ch> wrote:

Well, the problem is in scaladoc itself (eg link <https://lampsvn.epfl.ch/trac/scala/browser/scala/tags/R_2_9_0_final/src//library/scala/Function.scala#L1>)
The // wasn't a problem with Trac, but fisheye doesn't like it.

For the moment, I enabled again the browse source on the old URL and removed the redirection.
I will try to find a better solution.

On 05/18/2011 08:21 PM, Johannes Rudolph wrote:

Can we please get forwarders on https as well as http

And for source code as well, please. All the source links in Scaladoc
are right now broken even with http because there's a double slash
somewhere in the path.

--
Fabien Salvi

--
----------------------------------------------
Martin Odersky
Prof., EPFL and CEO, Typesafe
PSED, 1015 Lausanne, Switzerland
Tel. EPFL: +41 21 693 6863
Tel. Typesafe: +41 21 691 4967

While on the subject, it makes sense if issues were assigned by default to the owner of the affected component. Groups could also be created to act as the owners here, if that helps.

On 19 May 2011 17:15, martin odersky <martin.odersky@epfl.ch> wrote:

One thing that would be good to have is filter the list of possible assignees to Scala committers. It's quite hard to go through the list of everyone who's registered when you want top assign a ticket to someone.

Cheers

 -- Martin


On Thu, May 19, 2011 at 10:28 AM, Fabien Salvi <fabien.salvi@epfl.ch> wrote:

Well, the problem is in scaladoc itself (eg link <https://lampsvn.epfl.ch/trac/scala/browser/scala/tags/R_2_9_0_final/src//library/scala/Function.scala#L1>)
The // wasn't a problem with Trac, but fisheye doesn't like it.

For the moment, I enabled again the browse source on the old URL and removed the redirection.
I will try to find a better solution.

On 05/18/2011 08:21 PM, Johannes Rudolph wrote:

Can we please get forwarders on https as well as http

And for source code as well, please. All the source links in Scaladoc
are right now broken even with http because there's a double slash
somewhere in the path.

--
Fabien Salvi

--
----------------------------------------------
Martin Odersky
Prof., EPFL and CEO, Typesafe
PSED, 1015 Lausanne, Switzerland
Tel. EPFL: +41 21 693 6863
Tel. Typesafe: +41 21 691 4967

--
Kevin Wright

gtalk / msn : kev.lee.wright@gmail.comkev.lee.wright@gmail.commail: kevin.wright@scalatechnology.com
vibe / skype: kev.lee.wrightquora: http://www.quora.com/Kevin-Wright
twitter: @thecoda

"My point today is that, if we wish to count lines of code, we should not regard them as "lines produced" but as "lines spent": the current conventional wisdom is so foolish as to book that count on the wrong side of the ledger" ~ Dijkstra

Perhaps a new "Website and Tools" top-level project is needed, with "Website", "Confluence", "Jira", "Mailing Lists", "Jenkins", etc. as components.  Then we'd have an obvious place for this sort of suggestion, and it would keep some noise away from the main project at the same time.


On 19 May 2011 17:23, Kevin Wright <kev.lee.wright@gmail.com> wrote:

While on the subject, it makes sense if issues were assigned by default to the owner of the affected component. Groups could also be created to act as the owners here, if that helps.

On 19 May 2011 17:15, martin odersky <martin.odersky@epfl.ch> wrote:

One thing that would be good to have is filter the list of possible assignees to Scala committers. It's quite hard to go through the list of everyone who's registered when you want top assign a ticket to someone.

Cheers

 -- Martin


On Thu, May 19, 2011 at 10:28 AM, Fabien Salvi <fabien.salvi@epfl.ch> wrote:

Well, the problem is in scaladoc itself (eg link <https://lampsvn.epfl.ch/trac/scala/browser/scala/tags/R_2_9_0_final/src//library/scala/Function.scala#L1>)
The // wasn't a problem with Trac, but fisheye doesn't like it.

For the moment, I enabled again the browse source on the old URL and removed the redirection.
I will try to find a better solution.

On 05/18/2011 08:21 PM, Johannes Rudolph wrote:

Can we please get forwarders on https as well as http

And for source code as well, please. All the source links in Scaladoc
are right now broken even with http because there's a double slash
somewhere in the path.

--
Fabien Salvi

--
----------------------------------------------
Martin Odersky
Prof., EPFL and CEO, Typesafe
PSED, 1015 Lausanne, Switzerland
Tel. EPFL: +41 21 693 6863
Tel. Typesafe: +41 21 691 4967

--
Kevin Wright

gtalk / msn : kev.lee.wright@gmail.com kev.lee.wright@gmail.commail: kevin.wright@scalatechnology.com
vibe / skype: kev.lee.wrightquora: http://www.quora.com/Kevin-Wright
twitter: @thecoda

"My point today is that, if we wish to count lines of code, we should not regard them as "lines produced" but as "lines spent": the current conventional wisdom is so foolish as to book that count on the wrong side of the ledger" ~ Dijkstra

--
Kevin Wright

gtalk / msn : kev.lee.wright@gmail.comkev.lee.wright@gmail.commail: kevin.wright@scalatechnology.com
vibe / skype: kev.lee.wrightquora: http://www.quora.com/Kevin-Wright
twitter: @thecoda

"My point today is that, if we wish to count lines of code, we should not regard them as "lines produced" but as "lines spent": the current conventional wisdom is so foolish as to book that count on the wrong side of the ledger" ~ Dijkstra

Indeed - would be good to split out the Standard Library into sub-components as well (e.g. collections, control, actors, parallel, parsing, swing, misc)

Date: Thu, 19 May 2011 17:23:51 +0100
Subject: Re: [scala-internals] Re: Trac -> Jira
From: kev.lee.wright@gmail.com
To: scala-internals@googlegroups.com
CC: johannes.rudolph@googlemail.com; lukas.rytz@epfl.ch

While on the subject, it makes sense if issues were assigned by default to the owner of the affected component. Groups could also be created to act as the owners here, if that helps.

On 19 May 2011 17:15, martin odersky <martin.odersky@epfl.ch> wrote:

One thing that would be good to have is filter the list of possible assignees to Scala committers. It's quite hard to go through the list of everyone who's registered when you want top assign a ticket to someone.

Cheers

 -- Martin


On Thu, May 19, 2011 at 10:28 AM, Fabien Salvi <fabien.salvi@epfl.ch> wrote:

Well, the problem is in scaladoc itself (eg link <https://lampsvn.epfl.ch/trac/scala/browser/scala/tags/R_2_9_0_final/src//library/scala/Function.scala#L1>)
The // wasn't a problem with Trac, but fisheye doesn't like it.

For the moment, I enabled again the browse source on the old URL and removed the redirection.
I will try to find a better solution.

On 05/18/2011 08:21 PM, Johannes Rudolph wrote:

Can we please get forwarders on https as well as http

And for source code as well, please. All the source links in Scaladoc
are right now broken even with http because there's a double slash
somewhere in the path.

--
Fabien Salvi

--
----------------------------------------------
Martin Odersky
Prof., EPFL and CEO, Typesafe
PSED, 1015 Lausanne, Switzerland
Tel. EPFL: +41 21 693 6863
Tel. Typesafe: +41 21 691 4967

--
Kevin Wright

gtalk / msn : kev.lee.wright@gmail.comkev.lee.wright@gmail.commail: kevin.wright@scalatechnology.com
vibe / skype: kev.lee.wrightquora: http://www.quora.com/Kevin-Wright
twitter: @thecoda

"My point today is that, if we wish to count lines of code, we should not regard them as "lines produced" but as "lines spent": the current conventional wisdom is so foolish as to book that count on the wrong side of the ledger" ~ Dijkstra

All the revisions which in trac linked to the commit have become dead text, e.g.

https://issues.scala-lang.org/browse/SI-4582
(In r24962) Fix for Iterator flattening ....

The r24962 used to link to:

http://lampsvn.epfl.ch/trac/scala/changeset/24962

Now it is just an r and some numbers.

What is the status of the robot which used to look for "Closes #NNNN", update the ticket with the commit message and a link to the commit, and close the ticket? We were finally in a groove with connecting every bug with its fix. I can't go back to manually noting the revision. (And were I willing, right now they don't turn into hyperlinks anyway.) I'm assuming there are easyish substitutes or transitions for all these things and they just needed to be noticed.

Oh absolutely, Jira & Fisheye have some very good stuff for linking this all up, you can even see the actual code changes directly when browsing the ticket in Jira.
It just needs setting up...

On 19 May 2011 21:52, Paul Phillips <paulp@improving.org> wrote:

All the revisions which in trac linked to the commit have become dead text, e.g.

 https://issues.scala-lang.org/browse/SI-4582
 (In r24962) Fix for Iterator flattening ....

The r24962 used to link to:

 http://lampsvn.epfl.ch/trac/scala/changeset/24962

Now it is just an r and some numbers.

What is the status of the robot which used to look for "Closes #NNNN", update the ticket with the commit message and a link to the commit, and close the ticket? We were finally in a groove with connecting every bug with its fix.  I can't go back to manually noting the revision.  (And were I willing, right now they don't turn into hyperlinks anyway.) I'm assuming there are easyish substitutes or transitions for all these things and they just needed to be noticed.

--
Kevin Wright

gtalk / msn : kev.lee.wright@gmail.comkev.lee.wright@gmail.commail: kevin.wright@scalatechnology.com
vibe / skype: kev.lee.wrightquora: http://www.quora.com/Kevin-Wright
twitter: @thecoda

"My point today is that, if we wish to count lines of code, we should not regard them as "lines produced" but as "lines spent": the current conventional wisdom is so foolish as to book that count on the wrong side of the ledger" ~ Dijkstra

I`ll can do that, that`s fairly easy.

On Thu, May 19, 2011 at 18:15, martin odersky <martin.odersky@epfl.ch> wrote:

One thing that would be good to have is filter the list of possible assignees to Scala committers. It's quite hard to go through the list of everyone who's registered when you want top assign a ticket to someone.

Cheers

 -- Martin


On Thu, May 19, 2011 at 10:28 AM, Fabien Salvi <fabien.salvi@epfl.ch> wrote:

Well, the problem is in scaladoc itself (eg link <https://lampsvn.epfl.ch/trac/scala/browser/scala/tags/R_2_9_0_final/src//library/scala/Function.scala#L1>)
The // wasn't a problem with Trac, but fisheye doesn't like it.

For the moment, I enabled again the browse source on the old URL and removed the redirection.
I will try to find a better solution.

On 05/18/2011 08:21 PM, Johannes Rudolph wrote:

Can we please get forwarders on https as well as http

And for source code as well, please. All the source links in Scaladoc
are right now broken even with http because there's a double slash
somewhere in the path.

--
Fabien Salvi

--
----------------------------------------------
Martin Odersky
Prof., EPFL and CEO, Typesafe
PSED, 1015 Lausanne, Switzerland
Tel. EPFL: +41 21 693 6863
Tel. Typesafe: +41 21 691 4967

On Wed, May 18, 2011 at 3:01 PM, Daniel Sobral wrote:
> I'm rather fond of my Trac RSS feed through Google Reader, actually.
> Does JIRA has something like that?

The JIRA RSS feeds work quite well.

Still, I'd prefer to have e-mail notifications. Unfortunately I can't
find any obvious way to enable them for myself. Is there some global
configuration needed?

Cheers,

Miles

On Fri, May 20, 2011 at 9:02 AM, Miles Sabin wrote:
> On Wed, May 18, 2011 at 3:01 PM, Daniel Sobral wrote:
>> I'm rather fond of my Trac RSS feed through Google Reader, actually.
>> Does JIRA has something like that?
>
> The JIRA RSS feeds work quite well.
>
> Still, I'd prefer to have e-mail notifications. Unfortunately I can't
> find any obvious way to enable them for myself. Is there some global
> configuration needed?

Ahh ... it seems I'm still getting mails via scala-reports@epfl.ch ...
is that going to continue once the migration is complete?

Cheers,

Miles

Well, I didn't have much success for far with the rss feed thing. On
the filter side, I couldn't get a filter that would show only tickets
being opened -- the closed I could get was tickets in "opened" state,
which includes lots of conversation I'm completely uninterested in (if
I'm interested in a ticket, I'll add it to view).

On the RSS side, Google Reader doesn't like the URL provided for some
reason. It can't extract anything from it, and it doesn't even
recognize it as a feed if I enter it by hand.

Even worse, I told JIRA I wanted to subscribe through Google by
default, and now I can't find any place to undo that, which makes it
rather difficult to investigate what's happening.

So, did anyone get an RSS from JIRA to work on Google Reader? And can
anyone tell me how to subscribe only to tickets being opened?

On Wed, May 18, 2011 at 11:21, Kevin Wright wrote:
> Sure, Jira has RSS feeds.  You can even create your own based on some
> filter.
> (I'm sure a filter showing only Paul's commit messages would be immensely
> popular)
> I'd point you to a link, but the thing is currently hanging when I try to
> log in.
>
>
> On 18 May 2011 15:01, Daniel Sobral wrote:
>>
>> I'm rather fond of my Trac RSS feed through Google Reader, actually.
>> Does JIRA has something like that?
>>
>> On Wed, May 18, 2011 at 05:12, Kevin Wright
>> wrote:
>> > There's some rather nice Android/iOS apps available for talking to Jira
>> > if
>> > you do :)
>> > I use the Trac RSS feed via Google Reader at the moment, but it's not
>> > exactly the best UI going for this sort of thing.
>> >
>> >
>> > On 18 May 2011 09:07, Lukas Rytz wrote:
>> >>
>> >> sure, no reason not to i guess. let's get the basic thing running first
>> >> and then
>> >> we can see what needs to be added.
>> >>
>> >> On Wed, May 18, 2011 at 10:02, Kevin Wright
>> >> wrote:
>> >>>
>> >>> That's fantastic news!
>> >>> Will we also have Jira/Fisheye/Crucible set up to support connections
>> >>> via
>> >>> mylyn et. al?
>> >>>
>> >>> On 18 May 2011 06:56, Lukas Rytz wrote:
>> >>>>
>> >>>> Sure. I can send you a copy as well.
>> >>>> We will probably let it run for some time in read-only. However, this
>> >>>> might be on a different
>> >>>> address since for the current ticket URLs we'll put forwarders to
>> >>>> Jira.
>> >>>> Lukas
>> >>>>
>> >>>> On Wed, May 18, 2011 at 07:46, Paul Phillips
>> >>>> wrote:
>> >>>>>
>> >>>>> On 5/17/11 10:32 PM, Lukas Rytz wrote:
>> >>>>> > our plan is to migrate from trac to Jira this afternoon
>> >>>>> >
>> >>>>> >
>> >>>>> > .
>> >>>>> > For some time, trac will be
>> >>>>> > read-only and Jira not yet available.
>> >>>>> >
>> >>>>> > Let us know if you have any considerations.
>> >>>>>
>> >>>>> Can we make super sure to get a clean backup of trac?
>> >>>>>
>> >>>>> (And send me a copy?)
>> >>>>
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> Kevin Wright
>> >>>
>> >>> gtalk / msn : kev.lee.wright@gmail.com
>> >>> mail: kevin.wright@scalatechnology.com
>> >>> vibe / skype: kev.lee.wright
>> >>> quora: http://www.quora.com/Kevin-Wright
>> >>> twitter: @thecoda
>> >>>
>> >>> "My point today is that, if we wish to count lines of code, we should
>> >>> not
>> >>> regard them as "lines produced" but as "lines spent": the current
>> >>> conventional wisdom is so foolish as to book that count on the wrong
>> >>> side of
>> >>> the ledger" ~ Dijkstra
>> >>
>> >
>> >
>> >
>> > --
>> > Kevin Wright
>> >
>> > gtalk / msn : kev.lee.wright@gmail.com
>> > mail: kevin.wright@scalatechnology.com
>> > vibe / skype: kev.lee.wright
>> > quora: http://www.quora.com/Kevin-Wright
>> > twitter: @thecoda
>> >
>> > "My point today is that, if we wish to count lines of code, we should
>> > not
>> > regard them as "lines produced" but as "lines spent": the current
>> > conventional wisdom is so foolish as to book that count on the wrong
>> > side of
>> > the ledger" ~ Dijkstra
>> >
>>
>>
>>
>> --
>> Daniel C. Sobral
>>
>> I travel to the future all the time.
>
>
>
> --
> Kevin Wright
>
> gtalk / msn : kev.lee.wright@gmail.com
> mail: kevin.wright@scalatechnology.com
> vibe / skype: kev.lee.wright
> quora: http://www.quora.com/Kevin-Wright
> twitter: @thecoda
>
> "My point today is that, if we wish to count lines of code, we should not
> regard them as "lines produced" but as "lines spent": the current
> conventional wisdom is so foolish as to book that count on the wrong side of
> the ledger" ~ Dijkstra
>

On Fri, May 20, 2011 at 2:20 PM, Daniel Sobral wrote:
> On the RSS side, Google Reader doesn't like the URL provided for some
> reason. It can't extract anything from it, and it doesn't even
> recognize it as a feed if I enter it by hand.

If you're using Google Reader then you need to make sure you're giving
it a not-logged-in RSS feed URL ... Google Reader can't handle
authenticated feeds.

Cheers,

Miles

On Fri, May 20, 2011 at 10:26, Miles Sabin wrote:
> On Fri, May 20, 2011 at 2:20 PM, Daniel Sobral wrote:
>> On the RSS side, Google Reader doesn't like the URL provided for some
>> reason. It can't extract anything from it, and it doesn't even
>> recognize it as a feed if I enter it by hand.
>
> If you're using Google Reader then you need to make sure you're giving
> it a not-logged-in RSS feed URL ... Google Reader can't handle
> authenticated feeds.

Ok, I shared my filter, logged out, and then tried to add it to Google
Reader, and it still didn't work. I finally tracked the problem down
to one of the parameters in the URL:

https://issues.scala-lang.org/sr/jira.issueviews:searchrequest-rss/10105...

That tempMax. If I change it to 100, it works. WIth 1000, it doesn't.
Since there are only 175 entries in this filter, Google Reader's limit
must be much lower.

It seems that JIRA's watch emails are missing the In-Reply-To header
and additionally are prefixing the subject line of the emails with a
verb about what has changed. This, at least for GMail, makes it hard
to track which notification emails belong together. Can that be fixed?
Or does that work with any other email client correctly?

On Sat, May 21 2011, Johannes Rudolph wrote:

> It seems that JIRA's watch emails are missing the In-Reply-To header
> and additionally are prefixing the subject line of the emails with a
> verb about what has changed. This, at least for GMail, makes it hard
> to track which notification emails belong together. Can that be fixed?
> Or does that work with any other email client correctly?

Does help? JIRA can
certainly include the In-reply-to header.

I may be that the notificationinstance didn't get setup for the imported
issues. Newly created ones should at least have the proper header,
though.

David

On 5/19/11 1:52 PM, Paul Phillips wrote:
> What is the status of the robot which used to look for "Closes
> #NNNN", update the ticket with the commit message and a link to the
> commit, and close the ticket? We were finally in a groove with
> connecting every bug with its fix. I can't go back to manually
> noting the revision.

This is important. Who should I consider the responsible party for
restoring the previous state of affairs with auto-closing?

On a separate note, is there any way to make open and closed tickets
more visually distinct? The tiny status icon buried amongst any number
of other things is not something I can see without shifting my visual
focus to that element. The result is that I waste non-negligible
amounts of time, either on closed tickets I think are open, or on
frequent double checking that I'm not doing that.

These little things are not little for me and trac was already teetering
pretty close to the edge of unusability.

On Thu, May 19, 2011 at 22:52, Paul Phillips <paulp@improving.org> wrote:

All the revisions which in trac linked to the commit have become dead text, e.g.

 https://issues.scala-lang.org/browse/SI-4582
 (In r24962) Fix for Iterator flattening ....

The r24962 used to link to:

 http://lampsvn.epfl.ch/trac/scala/changeset/24962

Now it is just an r and some numbers.

Yes. Unfortunately the JIRA-Fisheye integration is not very mature yet. They seemto be actively working on it, however.
 

What is the status of the robot which used to look for "Closes #NNNN", update the ticket with the commit message and a link to the commit, and close the ticket?

Status is: for now it's not running..  

We were finally in a groove with connecting every bug with its fix.  I can't go back to manually noting the revision.  (And were I willing, right now they don't turn into hyperlinks anyway.) I'm assuming there are easyish substitutes or transitions for all these things and they just needed to be noticed.

I hope so.. I'll investigate more. 

On Sat, May 21, 2011 at 19:22, Johannes Rudolph <johannes.rudolph@googlemail.com> wrote:

It seems that JIRA's watch emails are missing the In-Reply-To header
and additionally are prefixing the subject line of the emails with a
verb about what has changed. This, at least for GMail, makes it hard
to track which notification emails belong together.

I find this annoying as well.. I'll have a look. 

Can that be fixed?
Or does that work with any other email client correctly?


--
Johannes

-----------------------------------------------
Johannes Rudolph
http://virtual-void.net

On Wed, May 18, 2011 at 02:32, Lukas Rytz wrote:
> Hi all,
> our plan is to migrate from trac to Jira this afternoon. For some time, trac
> will be
> read-only and Jira not yet available.
> Let us know if you have any considerations.

I have used the tag {code:scala} sometimes since the migration, but,
just today, it doesn't seem to work any longer. Any idea what might
have happened?