You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@marmotta.apache.org by Sebastian Schaffert <ss...@apache.org> on 2013/03/19 21:43:29 UTC
Re: svn commit: r1582 - /dev/incubator/marmotta/3.0.0-incubating/
Hi Daniel,
thanks for the friendly and helpful answer.
2013/3/19 Daniel Shahaf <d....@daniel.shahaf.name>
> You were expected to file an infra ticket prior to doing this (so that
> commit mails get set up correctly)
>
> Do docs say that?
>
No, not that I am aware of it. I was following the following guidelines:
-
http://incubator.apache.org/guides/releasemanagement.html#release-distribution
- http://www.apache.org/dev/release-publishing.html
- http://www.apache.org/dev/publishing-maven-artifacts.html
The first two documents both describe (among many other things) the SVN
distribution repository. None of these places mention that I would be
expected to file an INFRA ticket. Sorry if I overlooked yet-another
document when preparing the release. Could you please point me to it so we
can include it in our release process?
So to solve the situation, could you please setup the commit mails
correctly? I just realised that my colleague had already filed an issue
with INFRA last week, it just was not answered:
https://issues.apache.org/jira/browse/INFRA-5994
;-)
Greetings,
Sebastian
> sschaffert@apache.org wrote on Tue, Mar 19, 2013 at 17:00:32 -0000:
> > Author: sschaffert
> > Date: Tue Mar 19 17:00:08 2013
> > New Revision: 1582
> >
> > Log:
> > Apache Marmotta 3.0.0-incubating release candidate
> >
> > Added:
> > dev/incubator/marmotta/3.0.0-incubating/
> > dev/incubator/marmotta/3.0.0-incubating/KEYS
> >
> dev/incubator/marmotta/3.0.0-incubating/apache-marmotta-3.0.0-incubating-installer.tar.gz
> (with props)
>
Re: svn commit: r1582 - /dev/incubator/marmotta/3.0.0-incubating/
Posted by Sebastian Schaffert <ss...@apache.org>.
Hi Daniel,
first of all, thanks for all the work. It will really help future podlings.
2013/3/19 Daniel Shahaf <d....@daniel.shahaf.name>
>
> > >
> > > That's for two reasons: mailer config and svnwcsub setup. I've just
> > > made a tweak to the former - can you mkdir /release/incubator/marmotta
> > > and confirm that your commits@ list receives a notification of that?
> > >
> >
> > I tried it and the mail was delivered correctly. Thanks!
> >
>
> Cool. I just made a few more config changes that, among other things,
> mean future podlings don't need infra interventions for mailer config
> during podling dist dir creation. It shouldn't cause any visible
> difference, but if you notice any oddities (eg, missing commit mails),
> let us know.
>
> Specifically, _for @podling.i.a.o podlings only_, the project can now
> create the dist dir for itself. This doesn't apply to TLPs nor to
> "old-style" podlings.
>
Great. Does this mean we can leave the documentation as it is (i.e. no need
to create a ticket)? Are all future podlings going to be created in the
"new style"?
>
> >
> > >
> > > I'm inclined to leave the latter as-is, though: one svnwcsub line per
> > > podling. Which means the need for a jira ticket remains.
> > >
> > > Can you patch the incubator docs, then?
> > >
> >
> > Unfortunately this is out of my scope, I am just the release manager for
> > Marmotta and can only make suggestions to the incubator PMC. I will
> suggest
> > a patch to the mailinglist tomorrow.
> >
>
> Dunno how they work; maybe you should just commit to CMS and ask the
> list to review it on staging before you publish.
>
> Or maybe the documentation belongs on /dev/infra-contact (or
> /dev/release)? Things like the above distinction (which projects
> should/shouldn't mkdir their own dist dir) should be documented on the
> infra pages, IMO.
>
Never hurts to have it in two places, especially the release guide for
podlings (because this is obviously the first document that is checked).
The document says that suggestions for improvement should be sent to the
incubator general mailing list, so I'll do that if after your changes the
ticket is still necessary (see above).
>
> > >
> > > > - http://www.apache.org/dev/release-publishing.html
> > > > - http://www.apache.org/dev/publishing-maven-artifacts.html
> > > >
> > > > The first two documents both describe (among many other things) the
> SVN
> > > > distribution repository. None of these places mention that I would be
> > > > expected to file an INFRA ticket. Sorry if I overlooked yet-another
> > > > document when preparing the release. Could you please point me to it
> so
> > > we
> > > > can include it in our release process?
> > > >
> > >
> > > For starters http://www.apache.org/dev/release.
> > >
> > > There's no clear place explaining "you need to talk to us" (that's more
> > > http://www.apache.org/dev/infra-contact#requesting-podling material),
> > > but I suppose we could add a paragraph about that to
> > > http://www.apache.org/dev/release#heads-up. Or just change the authz
> > > file so podlings _can't_ create their own dist dirs.
> > >
> >
> > Maybe the best option would be to somewhere have a checklist which
> services
> > are actually to be requested for a podling. Would have made it easier for
> > us. I think the first link (...#requesting-podling) is the best place for
> > this.
> >
>
> Have you got concrete improvement suggestions? (If you do, feel free to
> ask this list to review them pre-commit or pre-publish.) From my POV,
> the most important thing to clarify is that the mailing lists must have
> been CREATED (not only requested) before things that email them are
> created[1].
>
In this concrete case, the mailinglist has been in place already for two
months. The only thing that was apparently missing was the forward of the
commit message to the list. So my suggestion is to have a table that lists:
- what services from INFRA are strictly required for every project (and how
the tickets should look like)
- what services can optionally be provided by INFRA for a project (e.g.
Nexus or Jenkins)
Unfortunately I don't have the complete overview, so I'd prefer someone
with more experience in the ASF to do a concrete suggestion.
Greetings,
Sebastian
Re: svn commit: r1582 - /dev/incubator/marmotta/3.0.0-incubating/
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Sebastian Schaffert wrote on Tue, Mar 19, 2013 at 22:18:03 +0100:
> Hi Daniel,
>
> Thanks for setting this up so quickly!
>
> 2013/3/19 Daniel Shahaf <d....@daniel.shahaf.name>
>
> > Sebastian Schaffert wrote on Tue, Mar 19, 2013 at 21:43:29 +0100:
> > > Hi Daniel,
> > >
> > > thanks for the friendly and helpful answer.
> > >
> > > 2013/3/19 Daniel Shahaf <d....@daniel.shahaf.name>
> > >
> > > > You were expected to file an infra ticket prior to doing this (so that
> > > > commit mails get set up correctly)
> > > >
> > > > Do docs say that?
> > > >
> > >
> > > No, not that I am aware of it. I was following the following guidelines:
> > > -
> > >
> > http://incubator.apache.org/guides/releasemanagement.html#release-distribution
> >
> > Right. And
> >
> > http://incubator.apache.org/guides/releasemanagement.html#understanding-upload
> > says "podling dist dir" and links to a definition of that. One or both of
> > those places should probably say that you may not create it yourself and
> > need instead to file a jira.
> >
>
> This would be very helpful, yes. :)
>
>
> >
> > That's for two reasons: mailer config and svnwcsub setup. I've just
> > made a tweak to the former - can you mkdir /release/incubator/marmotta
> > and confirm that your commits@ list receives a notification of that?
> >
>
> I tried it and the mail was delivered correctly. Thanks!
>
Cool. I just made a few more config changes that, among other things,
mean future podlings don't need infra interventions for mailer config
during podling dist dir creation. It shouldn't cause any visible
difference, but if you notice any oddities (eg, missing commit mails),
let us know.
Specifically, _for @podling.i.a.o podlings only_, the project can now
create the dist dir for itself. This doesn't apply to TLPs nor to
"old-style" podlings.
>
> >
> > I'm inclined to leave the latter as-is, though: one svnwcsub line per
> > podling. Which means the need for a jira ticket remains.
> >
> > Can you patch the incubator docs, then?
> >
>
> Unfortunately this is out of my scope, I am just the release manager for
> Marmotta and can only make suggestions to the incubator PMC. I will suggest
> a patch to the mailinglist tomorrow.
>
Dunno how they work; maybe you should just commit to CMS and ask the
list to review it on staging before you publish.
Or maybe the documentation belongs on /dev/infra-contact (or
/dev/release)? Things like the above distinction (which projects
should/shouldn't mkdir their own dist dir) should be documented on the
infra pages, IMO.
> >
> > > - http://www.apache.org/dev/release-publishing.html
> > > - http://www.apache.org/dev/publishing-maven-artifacts.html
> > >
> > > The first two documents both describe (among many other things) the SVN
> > > distribution repository. None of these places mention that I would be
> > > expected to file an INFRA ticket. Sorry if I overlooked yet-another
> > > document when preparing the release. Could you please point me to it so
> > we
> > > can include it in our release process?
> > >
> >
> > For starters http://www.apache.org/dev/release.
> >
> > There's no clear place explaining "you need to talk to us" (that's more
> > http://www.apache.org/dev/infra-contact#requesting-podling material),
> > but I suppose we could add a paragraph about that to
> > http://www.apache.org/dev/release#heads-up. Or just change the authz
> > file so podlings _can't_ create their own dist dirs.
> >
>
> Maybe the best option would be to somewhere have a checklist which services
> are actually to be requested for a podling. Would have made it easier for
> us. I think the first link (...#requesting-podling) is the best place for
> this.
>
Have you got concrete improvement suggestions? (If you do, feel free to
ask this list to review them pre-commit or pre-publish.) From my POV,
the most important thing to clarify is that the mailing lists must have
been CREATED (not only requested) before things that email them are
created[1].
Thanks
Daniel
[1] that includes "before mkdir /repos/asf/incubator/podling", as well
as "before mkdir /repos/dist/*/incubator/podling" (that's a mistake
people are unlikely to make, IMO) and "before account requests are made"
(those are CC'd to IPMC, but I imagine that creating the private@ list
first, then populating it with initial PPMCers, _then_ making the
account requests would provide better oversight on their contents)
Re: svn commit: r1582 - /dev/incubator/marmotta/3.0.0-incubating/
Posted by Sebastian Schaffert <ss...@apache.org>.
Hi Daniel,
Thanks for setting this up so quickly!
2013/3/19 Daniel Shahaf <d....@daniel.shahaf.name>
> Sebastian Schaffert wrote on Tue, Mar 19, 2013 at 21:43:29 +0100:
> > Hi Daniel,
> >
> > thanks for the friendly and helpful answer.
> >
> > 2013/3/19 Daniel Shahaf <d....@daniel.shahaf.name>
> >
> > > You were expected to file an infra ticket prior to doing this (so that
> > > commit mails get set up correctly)
> > >
> > > Do docs say that?
> > >
> >
> > No, not that I am aware of it. I was following the following guidelines:
> > -
> >
> http://incubator.apache.org/guides/releasemanagement.html#release-distribution
>
> Right. And
>
> http://incubator.apache.org/guides/releasemanagement.html#understanding-upload
> says "podling dist dir" and links to a definition of that. One or both of
> those places should probably say that you may not create it yourself and
> need instead to file a jira.
>
This would be very helpful, yes. :)
>
> That's for two reasons: mailer config and svnwcsub setup. I've just
> made a tweak to the former - can you mkdir /release/incubator/marmotta
> and confirm that your commits@ list receives a notification of that?
>
I tried it and the mail was delivered correctly. Thanks!
>
> I'm inclined to leave the latter as-is, though: one svnwcsub line per
> podling. Which means the need for a jira ticket remains.
>
> Can you patch the incubator docs, then?
>
Unfortunately this is out of my scope, I am just the release manager for
Marmotta and can only make suggestions to the incubator PMC. I will suggest
a patch to the mailinglist tomorrow.
>
> > - http://www.apache.org/dev/release-publishing.html
> > - http://www.apache.org/dev/publishing-maven-artifacts.html
> >
> > The first two documents both describe (among many other things) the SVN
> > distribution repository. None of these places mention that I would be
> > expected to file an INFRA ticket. Sorry if I overlooked yet-another
> > document when preparing the release. Could you please point me to it so
> we
> > can include it in our release process?
> >
>
> For starters http://www.apache.org/dev/release.
>
> There's no clear place explaining "you need to talk to us" (that's more
> http://www.apache.org/dev/infra-contact#requesting-podling material),
> but I suppose we could add a paragraph about that to
> http://www.apache.org/dev/release#heads-up. Or just change the authz
> file so podlings _can't_ create their own dist dirs.
>
Maybe the best option would be to somewhere have a checklist which services
are actually to be requested for a podling. Would have made it easier for
us. I think the first link (...#requesting-podling) is the best place for
this.
>
> > So to solve the situation, could you please setup the commit mails
> > correctly? I just realised that my colleague had already filed an issue
>
> Done. But leave the jira open please, svnwcsub still needs to be set up
> for your ^/release area.
>
Ok.
>
> > with INFRA last week, it just was not answered:
> >
> > https://issues.apache.org/jira/browse/INFRA-5994
> >
>
> It's in the queue. Actually there are about 4 "create an svnpubsub dist
> dir" jiras in the queue, which is good for us (we can batch them - this
> particular task isn't scripted yet).
>
> Great :-)
Greetings
Sebastian
Re: svn commit: r1582 - /dev/incubator/marmotta/3.0.0-incubating/
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Sebastian Schaffert wrote on Tue, Mar 19, 2013 at 21:43:29 +0100:
> Hi Daniel,
>
> thanks for the friendly and helpful answer.
>
> 2013/3/19 Daniel Shahaf <d....@daniel.shahaf.name>
>
> > You were expected to file an infra ticket prior to doing this (so that
> > commit mails get set up correctly)
> >
> > Do docs say that?
> >
>
> No, not that I am aware of it. I was following the following guidelines:
> -
> http://incubator.apache.org/guides/releasemanagement.html#release-distribution
Right. And
http://incubator.apache.org/guides/releasemanagement.html#understanding-upload
says "podling dist dir" and links to a definition of that. One or both of
those places should probably say that you may not create it yourself and
need instead to file a jira.
That's for two reasons: mailer config and svnwcsub setup. I've just
made a tweak to the former - can you mkdir /release/incubator/marmotta
and confirm that your commits@ list receives a notification of that?
I'm inclined to leave the latter as-is, though: one svnwcsub line per
podling. Which means the need for a jira ticket remains.
Can you patch the incubator docs, then?
> - http://www.apache.org/dev/release-publishing.html
> - http://www.apache.org/dev/publishing-maven-artifacts.html
>
> The first two documents both describe (among many other things) the SVN
> distribution repository. None of these places mention that I would be
> expected to file an INFRA ticket. Sorry if I overlooked yet-another
> document when preparing the release. Could you please point me to it so we
> can include it in our release process?
>
For starters http://www.apache.org/dev/release.
There's no clear place explaining "you need to talk to us" (that's more
http://www.apache.org/dev/infra-contact#requesting-podling material),
but I suppose we could add a paragraph about that to
http://www.apache.org/dev/release#heads-up. Or just change the authz
file so podlings _can't_ create their own dist dirs.
> So to solve the situation, could you please setup the commit mails
> correctly? I just realised that my colleague had already filed an issue
Done. But leave the jira open please, svnwcsub still needs to be set up
for your ^/release area.
> with INFRA last week, it just was not answered:
>
> https://issues.apache.org/jira/browse/INFRA-5994
>
It's in the queue. Actually there are about 4 "create an svnpubsub dist
dir" jiras in the queue, which is good for us (we can batch them - this
particular task isn't scripted yet).
> ;-)
>
>
> Greetings,
>
> Sebastian
>
>
>
> > sschaffert@apache.org wrote on Tue, Mar 19, 2013 at 17:00:32 -0000:
> > > Author: sschaffert
> > > Date: Tue Mar 19 17:00:08 2013
> > > New Revision: 1582
> > >
> > > Log:
> > > Apache Marmotta 3.0.0-incubating release candidate
> > >
> > > Added:
> > > dev/incubator/marmotta/3.0.0-incubating/
> > > dev/incubator/marmotta/3.0.0-incubating/KEYS
> > >
> > dev/incubator/marmotta/3.0.0-incubating/apache-marmotta-3.0.0-incubating-installer.tar.gz
> > (with props)
> >
Re: svn commit: r1582 - /dev/incubator/marmotta/3.0.0-incubating/
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Sebastian Schaffert wrote on Tue, Mar 19, 2013 at 22:20:42 +0100:
> Sorry, this was not my intention (I did not actually realize that
> infrastructure-cvs is a private list). I just wanted to send this also to
FTR... http://www.apache.org/dev/infra-mail documents that. :)
Re: svn commit: r1582 - /dev/incubator/marmotta/3.0.0-incubating/
Posted by Sebastian Schaffert <ss...@apache.org>.
Hi Daniel,
2013/3/19 Daniel Shahaf <d....@daniel.shahaf.name>
>
> Sebastian Schaffert wrote on Tue, Mar 19, 2013 at 21:43:29 +0100:
> > 2013/3/19 Daniel Shahaf <d....@daniel.shahaf.name>
> >
> > > You were expected to file an infra ticket prior to doing this (so that
> > > commit mails get set up correctly)
> > >
> > > Do docs say that?
>
> BTW, Sebastian, as you know you may not forward to a public list a mail
> sent to a private list without all quotee's permissions.
>
> My reply above was sent to a private list and you quoted it on a public
> list. On this instance I don't mind, but don't do that again please.
>
Sorry, this was not my intention (I did not actually realize that
infrastructure-cvs is a private list). I just wanted to send this also to
the development mailinglist to have a proper documentation for the future
(and give the other developers the same level of information). My fault.
Greetings,
Sebastian
Re: svn commit: r1582 - /dev/incubator/marmotta/3.0.0-incubating/
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Sebastian Schaffert wrote on Tue, Mar 19, 2013 at 21:43:29 +0100:
> 2013/3/19 Daniel Shahaf <d....@daniel.shahaf.name>
>
> > You were expected to file an infra ticket prior to doing this (so that
> > commit mails get set up correctly)
> >
> > Do docs say that?
BTW, Sebastian, as you know you may not forward to a public list a mail
sent to a private list without all quotee's permissions.
My reply above was sent to a private list and you quoted it on a public
list. On this instance I don't mind, but don't do that again please.