RFC: URLs for docs and released bits from CI

[Tim Flink]

I submitted a revision today which makes some slight modification to
how the doit.py script is building docs, rpms and tarballs.

https://phab.qadevel.cloud.fedoraproject.org/D1012

My intention is to get this deployed to a non-staging setup soon but I
wanted to reach out to see if anyone had an issue for the URLs that
would end up being used.

https://baseurl/docs/

This path would contain docs for  built per branch for
non-master branches and per-release-version when triggered on the
master branch. The 'latest' symlink will always be updated to point at
the most recent build on the master branch


https://baseurl/releases/

Pretty much the same thing as for docs but with the rpms, srpms and
tarball(s) created during the CI build.

Does this seem sane to everyone? Any comments/questions/suggestions? I'd
like to get the auto-docs functionality deployed soon - hopefully right
after F25 beta freeze is over.

Tim


pgpfHNtiAeCOS.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

Re: 2016-09-14 @ 14:00 UTC - QA Tools Video "Standup" Meeting

[Josef Skladanka]

I'd rather go with the option no. 1, but I don't really care that much
either way. So if one option suits you guys better, I'll comply.

J.

On Thu, Sep 22, 2016 at 9:59 AM, Martin Krizek  wrote:

> - Original Message -
> > From: "Tim Flink" 
> > To: qa-devel@lists.fedoraproject.org
> > Sent: Wednesday, September 14, 2016 4:59:49 PM
> > Subject: Re: 2016-09-14 @ 14:00 UTC -  QA Tools Video "Standup" Meeting
> >
> > 
> >
> > One of the topics that came up was how often to do these video
> > meetings. Having additional weekly meetings via video seems like
> > overkill but if there's an appropriate in-depth topic, meeting via
> > video to talk instead of type would be useful.
> >
> > The two options we came up with are:
> >
> > 1. Switch the first qadevel meeting of every month to be via video,
> >making sure that an agenda is sent out early enough for folks to be
> >prepared.
> >
> > 2. Pencil in a video meeting once or twice a month on the Wednesday
> >after qadevel meetings. Ask for video topics during the qadevel
> >meeting and on email. If there are enough topics suggested which
> >would benefit from talking instead of typing, meet on the following
> >Wednesday to discuss via video. If there is no need to meet via
> >video, skip it.
> >
> > I realize that I'm changing things up a little bit from what we were
> > talking about at the end of the meeting but I have a small concern
> > about option 1 - one of the issues that we had today is that folks
> > weren't prepared because we didn't set an agenda.
> >
> > If we switch one qadevel meeting per month  to video, how do we want to
> > handle setting the agenda early enough so that participants have enough
> > time to prepare?
> >
> > Any thoughts or preferences?
> >
>
> My vote would be for the option 2., mostly because the video meeting can
> be easily skipped if we don't have any topics to discuss and that
> setting an agenda would be done on a set time (Monday meeting). It seems
> to me that this could work well.
>
>
> Thanks,
> Martin
> ___
> qa-devel mailing list -- qa-devel@lists.fedoraproject.org
> To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org
>
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

Re: 2016-09-14 @ 14:00 UTC - QA Tools Video "Standup" Meeting

[Martin Krizek]

- Original Message -
> From: "Tim Flink" 
> To: qa-devel@lists.fedoraproject.org
> Sent: Wednesday, September 14, 2016 4:59:49 PM
> Subject: Re: 2016-09-14 @ 14:00 UTC -  QA Tools Video "Standup" Meeting
> 
> 
> 
> One of the topics that came up was how often to do these video
> meetings. Having additional weekly meetings via video seems like
> overkill but if there's an appropriate in-depth topic, meeting via
> video to talk instead of type would be useful.
> 
> The two options we came up with are:
> 
> 1. Switch the first qadevel meeting of every month to be via video,
>making sure that an agenda is sent out early enough for folks to be
>prepared.
> 
> 2. Pencil in a video meeting once or twice a month on the Wednesday
>after qadevel meetings. Ask for video topics during the qadevel
>meeting and on email. If there are enough topics suggested which
>would benefit from talking instead of typing, meet on the following
>Wednesday to discuss via video. If there is no need to meet via
>video, skip it.
> 
> I realize that I'm changing things up a little bit from what we were
> talking about at the end of the meeting but I have a small concern
> about option 1 - one of the issues that we had today is that folks
> weren't prepared because we didn't set an agenda.
> 
> If we switch one qadevel meeting per month  to video, how do we want to
> handle setting the agenda early enough so that participants have enough
> time to prepare?
> 
> Any thoughts or preferences?
> 

My vote would be for the option 2., mostly because the video meeting can
be easily skipped if we don't have any topics to discuss and that
setting an agenda would be done on a set time (Monday meeting). It seems
to me that this could work well.


Thanks,
Martin
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org