On Sun, 7 Oct 2018 at 10:58, Neil C Smith wrote:
> How about a compromise? Let's pull this and manage it in the asf-site
> branch directly as and until we have an automated approach ready?
OK, pulled to asf-site. I realise that was suggested in the PR, and
we know it at least needs to be in
Hi,
On Sun, 7 Oct 2018 at 07:32, Antonio wrote:
> On 10/7/18 12:22 AM, Neil C Smith wrote:
> > I was really
> > going for the simplest and quickest approach here for immediate needs.
>
> The idea is to avoid having too many files in the master branch.
OK, I understand what you're getting at.
On 10/7/18 12:22 AM, Neil C Smith wrote:
Hi,
On Sat, 6 Oct 2018, 21:16 Antonio Vieiro, wrote:
For 9.0 we could use a branch named "9.0-vc3" (same as the tag in
incubator-netbeans).
I'm not sure I understand the reasoning for branching like that? Surely we
could just as easily tag
Hi,
On Sat, 6 Oct 2018, 21:16 Antonio Vieiro, wrote:
> For 9.0 we could use a branch named "9.0-vc3" (same as the tag in
> incubator-netbeans).
I'm not sure I understand the reasoning for branching like that? Surely we
could just as easily tag master? What's your thoughts behind it? It might
I was thinking we could merge to another branch instead of to master.
For 9.0 we could use a branch named "9.0-vc3" (same as the tag in
incubator-netbeans). In fact we could update the jenkins release job
to push the javadoc to this new repo as well. And so on with the rest
of releases.
We then
> On **GitHub**, Antonio wrote:
> Do we want to merge this into master? Or asf-site instead? How is web
> publishing set up? Can we discuss in the mailing list?
OK, bringing that discussion onto the mailing list (although I do need
to fix where the GitHub notifications are going, so may be here
On Thu, 4 Oct 2018 at 20:32, Geertjan Wielenga
wrote:
>
> If we want mentors to do something we need to start a new thread with
> Mentors in the subject line.
I added it to the subject line, but it seems that might not be
registering as a new thread. OK, will take 2!
Thanks,
Neil
If we want mentors to do something we need to start a new thread with
Mentors in the subject line.
Great we’re making progress on the javadoc!
Gj
On Thursday, October 4, 2018, Neil C Smith wrote:
> On Thu, 4 Oct 2018 at 19:29, Neil C Smith wrote:
> >
> > On Thu, 4 Oct 2018 at 19:19,
On Thu, 4 Oct 2018 at 19:29, Neil C Smith wrote:
>
> On Thu, 4 Oct 2018 at 19:19, Antonio wrote:
> >
> > Yep. infra.chat is awesome. You can have things solved within the minute!
> >
>
> Hi, yes, just about to. But I was confused because according to the
> wiki edits, infra told you to use
On Thu, 4 Oct 2018 at 19:19, Antonio wrote:
>
> Yep. infra.chat is awesome. You can have things solved within the minute!
>
Hi, yes, just about to. But I was confused because according to the
wiki edits, infra told you to use self-serve?!
Best wishes,
Neil
Yes indeed! I'm big fan of it as well.
On 10/04/2018 11:19 AM, Antonio wrote:
Yep. infra.chat is awesome. You can have things solved within the minute!
On 04/10/18 15:16, Geertjan Wielenga wrote:
Any questions re infrastructure, and permissions, just pop over to
infra.chat and check there.
Yep. infra.chat is awesome. You can have things solved within the minute!
On 04/10/18 15:16, Geertjan Wielenga wrote:
Any questions re infrastructure, and permissions, just pop over to
infra.chat and check there.
Gj
On Thu, Oct 4, 2018 at 3:05 PM Neil C Smith wrote:
On Wed, 3 Oct 2018 at
Any questions re infrastructure, and permissions, just pop over to
infra.chat and check there.
Gj
On Thu, Oct 4, 2018 at 3:05 PM Neil C Smith wrote:
> On Wed, 3 Oct 2018 at 12:44, Antonio wrote:
> > I think it's worth exploring this path. Let me know if I can be of help
> > on this.
>
> OK,
On Wed, 3 Oct 2018 at 12:44, Antonio wrote:
> I think it's worth exploring this path. Let me know if I can be of help
> on this.
OK, looked at setting up the repo for this via self-serve as you
mentioned from an earlier infra chat, but looks like we don't have
permission to do that ourselves?!
On 03/10/18 00:10, Antonio wrote:
Hi all,
We now have https://netbeans.apache.org/javadoc/dev/index.html
[...]
- Update the current jbake website jenkins job to avoid removing the
"javadoc" directory whenever a change is published (pushing to the
website will remove javadocs right now).
Hi Neil,
I think it's worth exploring this path. Let me know if I can be of help
on this.
Cheers,
Antonio
El 03/10/2018 a las 8:38, Neil C Smith escribió:
Hi,
On Tue, 2 Oct 2018 at 23:11, Antonio wrote:
We now have https://netbeans.apache.org/javadoc/dev/index.html
...
Jenkins job is at
Hi,
On Tue, 2 Oct 2018 at 23:11, Antonio wrote:
> We now have https://netbeans.apache.org/javadoc/dev/index.html
>...
> Jenkins job is at
> https://builds.apache.org/view/Incubator%20Projects/job/incubator-netbeans-website-javadoc/
> the initial commit [3] is quite big: more than 13000 files and
Hi,
Adding 9.0 will require checking out the 9.0 branch, building javadoc
and publishing it. I don't think it's worth building a jenkins for this,
but it would be good having it for future NetBeans releases.
I think it's worth exploring the proxy approach Neil was talking about
in another
Awesome, this is great to see. If this works and is not problematic, let’s
do it. Re adding 9.0, what is needed to do that?
Gj
On Wednesday, October 3, 2018, Antonio wrote:
> Hi all,
>
> We now have https://netbeans.apache.org/javadoc/dev/index.html
>
> This is experimental. Things may be
Hi all,
We now have https://netbeans.apache.org/javadoc/dev/index.html
This is experimental. Things may be still syncing (if you see a 404
please retry). Note that we're uploading .zip files for each module
([1], [2]) as well.
Jenkins job is at
20 matches
Mail list logo
