- About Scala
- Documentation
- Code Examples
- Software
- Scala Developers
Nightly ScalaDoc
Tue, 2011-12-27, 17:09
I was looking today at the nightly Scaladoc when I noticed it linked to the 2.9.2 branch. Could we please have it pointing to trunk again?
And, by the way, there were dozens of improvements to the Scaladoc tool *and* to Scala API docs on trunk. Can we have them backported *before* 2.9.2 is out? I volunteer to track down all commits if the answer is positive.
--
Daniel C. Sobral
I travel to the future all the time.
And, by the way, there were dozens of improvements to the Scaladoc tool *and* to Scala API docs on trunk. Can we have them backported *before* 2.9.2 is out? I volunteer to track down all commits if the answer is positive.
--
Daniel C. Sobral
I travel to the future all the time.
Mon, 2012-01-09, 18:51
#2
Re: Nightly ScalaDoc
Hi,
any chance to fix this?
Thanks and bye,
Simon
any chance to fix this?
Thanks and bye,
Simon
Mon, 2012-01-09, 20:01
#3
Re: Nightly ScalaDoc
Feel free to open a verified pull request. Before one of us has a chance to get to this.
On Jan 9, 2012 12:49 PM, "Simon Ochsenreither" <simon.ochsenreither@googlemail.com> wrote:Hi,
any chance to fix this?
Thanks and bye,
Simon
Mon, 2012-01-09, 20:51
#4
Re: Nightly ScalaDoc
I have really no idea where the code doing it lives. It is not on GitHub afaik.
Mon, 2012-01-09, 22:01
#5
Re: Nightly ScalaDoc
On Mon, Jan 9, 2012 at 17:46, Simon Ochsenreither
wrote:
> I have really no idea where the code doing it lives. It is not on GitHub
> afaik.
Huh? AFAIK, scaladoc is part of the scala project, and, furthermore,
the doc improvements themselves are just commits on the libraries that
can be mostly cherry-picked.
Tue, 2012-01-10, 02:21
#6
Re: Nightly ScalaDoc
Sorry, I meant this:
Bye!
I was looking today at the nightly Scaladoc when I noticed it linked to the 2.9.2 branch. Could we please have it pointing to trunk again?
Bye!
Tue, 2012-01-10, 03:41
#7
Re: Nightly ScalaDoc
https://github.com/scala/scala.github.com and try http://scala.github.com.
On Tue, Jan 10, 2012 at 2:20 AM, Simon Ochsenreither
wrote:
> Sorry, I meant this:
>
>
>> I was looking today at the nightly Scaladoc when I noticed it linked to
>> the 2.9.2 branch. Could we please have it pointing to trunk again?
>
>
> Bye!
Tue, 2012-01-10, 03:51
#8
Re: Nightly ScalaDoc
Hi!
Do I miss something completely obvious?
Yes, the "Nightly" link in scala.github.com also uses 2.9.2 instead of trunk.
As far as I know the generation of the nightly ScalaDoc happens somewhere in Jenkins and that stuff is not on GitHub.
Maybe the person who has changed could just reverse it (or at least tell people why it was changed)?
Thanks and bye,
Simon
Do I miss something completely obvious?
Yes, the "Nightly" link in scala.github.com also uses 2.9.2 instead of trunk.
As far as I know the generation of the nightly ScalaDoc happens somewhere in Jenkins and that stuff is not on GitHub.
Maybe the person who has changed could just reverse it (or at least tell people why it was changed)?
Thanks and bye,
Simon
On Tue, Dec 27, 2011 at 8:09 AM, Daniel Sobral <dcsobral@gmail.com> wrote:
There's no reason we wouldn't include API doc improvements. With scaladoc it's the usual question of maintaining binary compatibility. You don't have to stop at finding the commits - there's a 2.9.x branch on github, you can send pull requests against that as well as against trunk.
I have been tagging commits I want in 2.9.2 as "2.9.2" on jira. That doesn't mean they will be in 2.9.2, it just means I want them in 2.9.2. There's nothing stopping other people from doing the same tagging, which may be a mixed blessing and if it's abused it will make me sad. Commits proposed for backporting should be localized bugfixes which are not obvious binary compatibility breakers. (It's not the end of the world if you're wrong about binary compat because the tool will catch it, but it saves time to exclude the impossible.)