Saturday, September 30, 2017, 12:28:39 PM, Daniel Dekany wrote: > Saturday, September 30, 2017, 3:39:24 AM, Woonsan Ko wrote: > >> On Mon, Sep 25, 2017 at 2:49 PM, Daniel Dekany <[email protected]> wrote: >>> Monday, September 25, 2017, 7:23:14 PM, Woonsan Ko wrote: >>> >>>> I'd like to volunteer for that. >>>> Assuming there's a voting process, I guess the release process will >>>> happen next week or afterward, right? >>> >>> The actual release yes, but the duty of the Release Manager is to take >>> care of the whole process. That's starting with checking if the thing >>> is ready and publishing it internally for a preview, then achieving >>> community consensus (which for us means a voting on dev@freemarker, >>> and if that passes then another voting on general@incubator), then >>> actually pushing the distribution. But >>> http://freemarker.org/committer-howto.html#making-releases describes >>> all these steps. (There are also official resources like >>> http://www.apache.org/dev/#releases and >>> http://incubator.apache.org/guides/releasemanagement.html, but the >>> point of the how-to is that you don't have to read them.) >>> >>> As you will note if you read the above, you will need a PGP signature >>> and certain rights to commit into some repos and to do things on >>> Nexus. So you will have to start with requesting those rights. >> >> I've added mine to KEYS files in >> dist.apache.org/repos/dist/{dev,release}/incubator/freemarker/. > > I'm not a PGP expert at all, so I really don't know if these have any > practical implications, but two things that I'm not sure about: > > - Wouldn't it be better to stick to only one of the two public keys? > > - The pub header in KEYS looks kind of unusual. It used to be like > "pub 4096R/82667DC1 2014-07-17", where the 82667DC1 is used on > several places to refer to the public key, like in sig-s and all. > > Last not least, someone from the ASF who knows you in person should > sign the key that you release with. The Ring of Trust thing, you > know... (I guess it's good enough if I do it, when the above key > question is settled.) > >> And, I was able to log on the Nexus and browse repository and staging >> repository. >> The next is to follow "The steps of making a release" section? > > I'm just investigating some backward compatibility issue,
Fixed it. BTW, before starting the vote, let me look at the upload/staged thing. Just in case... it's less "paper work" to fix any oversight then. > but otherwise yes. (I have updated it a bit BTW.) Are you using some > kind of instant messaging or chat room or such? E-mail will be too > slow I think. (Screen sharing and voice can come handy as well > sometimes. If you happen to use Skype, I'm there.) > > >> Regards, >> >> Woonsan >> >>> >>>> I'm asking this because my laptop got broken before the last week >>>> and I'm waiting for a new laptop to be delivered this week. If it is >>>> next week or afterward, I'll be prepared properly. >>> >>> If in the light of the above you are still willing to do this, I will >>> wait. >>> >>>> Regards, >>>> >>>> Woonsan >>>> >>>> On Wed, Sep 20, 2017 at 2:12 PM, Daniel Dekany <[email protected]> wrote: >>>>> Could somebody with commit rights volunteer for this? We have a >>>>> step-to-step guide >>>>> (http://freemarker.org/committer-howto.html#making-releases), and I >>>>> would be present to help with this (through Skype or whatever you >>>>> prefer). I want to see (and demonstrate) that in case I'm gone someone >>>>> else can do a release. >>>>> >>>>> Thanks a lot! >>>>> >>>>> -- >>>>> Best regards, >>>>> Daniel Dekany >>>>> >>>> >>> >>> -- >>> Thanks, >>> Daniel Dekany >>> >> > -- Thanks, Daniel Dekany
