You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pirk.apache.org by Ellison Anne Williams <ea...@apache.org> on 2016/08/30 15:50:49 UTC
Website Updates - Please Review
Hi,
Given that it's generally a mess to put website updates through the PR
system (due to the large number of auxiliary files changed - in the
hundreds...), I have made several updates to the Apache Pirk website and am
posting the list here so that folks can easily take a look and review. I'm
more than happy to make edits to the pages today as needed. If there is a
better way to do this, please let me know.
- Making Releases page updated to reflect our current release process:
http://pirk.incubator.apache.org/releasing
<http://pirk.incubator.apache.org/releasing>
- Keys link fixed from this page: http://pirk.incubator.
apache.org/downloads/ (fixes PIRK-60)
- News bar updated to reflect the first release: http://pirk.
incubator.apache.org/ (as well as the corresponding 'News' page
http://pirk.incubator.apache.org/news
<http://pirk.incubator.apache.org/news>)
- Javadocs updated: http://pirk.incubator.apache.org/javadocs/
- How to Contribute page updated to reflect license and notice checks:
http://pirk.incubator.apache.org/how_to_contribute
<http://pirk.incubator.apache.org/how_to_contribute>
Thanks!
Ellison Anne
Re: Website Updates - Please Review
Posted by Ellison Anne Williams <ea...@apache.org>.
Each time I had to rollback (yes, there were many - lol), I had already
executed 'mvn -Psigned_release release:perform' (go big or go home...or
rollback).
The way that the release instructions are currently written on the webpage,
the artifacts are validated after they have been pushed to the Nexus repo -
hence, necessitating the (2) set of steps outlined. To avoid a re-write of
the release and validation steps, I would prefer to leave it as-is for now.
On Tue, Aug 30, 2016 at 12:46 PM, Suneel Marthi <su...@gmail.com>
wrote:
> It depends at what stage in the release process u would want to rollback.
>
>
> 1. mvn -Psigned_release release:prepare
>
> then to rollback
>
> mvn -Psigned_release release:rollback
> mvn -Psigned_release release:clean
> git tag -d <tagname>
>
>
> 2. mvn -Psigned_release release:prepare
> mvn -Psigned_release release:perform
>
> to rollback the steps outlined in
> https://lists.apache.org/thread.html/c8acce2a20e8e2671d85fd8504bb2c
> 7c52ebb5159b955ec762754bc7@%3Cdev.pirk.apache.org%3E
> need to performed.
>
>
>
>
>
>
> On Tue, Aug 30, 2016 at 12:40 PM, Ellison Anne Williams <
> eawilliams@apache.org> wrote:
>
> > I never actually used 'mvn -Psigned_release release:rollback' to to roll
> > back the release -- I used the alternate steps that you gave here:
> > https://lists.apache.org/thread.html/c8acce2a20e8e2671d85fd8504bb2c
> > 7c52ebb5159b955ec762754bc7@%3Cdev.pirk.apache.org%3E
> >
> >
> >
> > On Tue, Aug 30, 2016 at 12:08 PM, Suneel Marthi <suneel.marthi@gmail.com
> >
> > wrote:
> >
> > > On Tue, Aug 30, 2016 at 12:05 PM, Suneel Marthi <
> suneel.marthi@gmail.com
> > >
> > > wrote:
> > >
> > > >
> > > >
> > > > On Tue, Aug 30, 2016 at 11:50 AM, Ellison Anne Williams <
> > > > eawilliams@apache.org> wrote:
> > > >
> > > >> Hi,
> > > >>
> > > >> Given that it's generally a mess to put website updates through the
> PR
> > > >> system (due to the large number of auxiliary files changed - in the
> > > >> hundreds...), I have made several updates to the Apache Pirk website
> > and
> > > >> am
> > > >> posting the list here so that folks can easily take a look and
> review.
> > > I'm
> > > >> more than happy to make edits to the pages today as needed. If there
> > is
> > > a
> > > >> better way to do this, please let me know.
> > > >>
> > > >> - Making Releases page updated to reflect our current release
> > > process:
> > > >> http://pirk.incubator.apache.org/releasing
> > > >> <http://pirk.incubator.apache.org/releasing>
> > > >>
> > > >
> > > > You may not want to hardcode orgapachepirk-1001 here, it could be
> > > > different for each staging Release Candidate - lets call it
> > > > orgapachepirk-xxxx instead.
> > > >
> > > > Under the Section Rollback Release:
> > >
> > > If the rollback needs to happen after release:prepare and before
> > > release:perform, the steps are:
> > >
> > > 1. mvn -Psigned_release release:rollback
> > > 2. mvn -Psigned_release release:clean
> > > 3. git tag -d <tagname>
> > >
> > >
> > > >
> > > >> - Keys link fixed from this page: http://pirk.incubator.
> > > >> apache.org/downloads/ (fixes PIRK-60)
> > > >> - News bar updated to reflect the first release: http://pirk.
> > > >> incubator.apache.org/ (as well as the corresponding 'News' page
> > > >> http://pirk.incubator.apache.org/news
> > > >> <http://pirk.incubator.apache.org/news>)
> > > >> - Javadocs updated: http://pirk.incubator.apache.org/javadocs/
> > > >> - How to Contribute page updated to reflect license and notice
> > > checks:
> > > >> http://pirk.incubator.apache.org/how_to_contribute
> > > >> <http://pirk.incubator.apache.org/how_to_contribute>
> > > >>
> > > >> Thanks!
> > > >>
> > > >> Ellison Anne
> > > >>
> > > >
> > > >
> > >
> >
>
Re: Website Updates - Please Review
Posted by Suneel Marthi <su...@gmail.com>.
It depends at what stage in the release process u would want to rollback.
1. mvn -Psigned_release release:prepare
then to rollback
mvn -Psigned_release release:rollback
mvn -Psigned_release release:clean
git tag -d <tagname>
2. mvn -Psigned_release release:prepare
mvn -Psigned_release release:perform
to rollback the steps outlined in
https://lists.apache.org/thread.html/c8acce2a20e8e2671d85fd8504bb2c7c52ebb5159b955ec762754bc7@%3Cdev.pirk.apache.org%3E
need to performed.
On Tue, Aug 30, 2016 at 12:40 PM, Ellison Anne Williams <
eawilliams@apache.org> wrote:
> I never actually used 'mvn -Psigned_release release:rollback' to to roll
> back the release -- I used the alternate steps that you gave here:
> https://lists.apache.org/thread.html/c8acce2a20e8e2671d85fd8504bb2c
> 7c52ebb5159b955ec762754bc7@%3Cdev.pirk.apache.org%3E
>
>
>
> On Tue, Aug 30, 2016 at 12:08 PM, Suneel Marthi <su...@gmail.com>
> wrote:
>
> > On Tue, Aug 30, 2016 at 12:05 PM, Suneel Marthi <suneel.marthi@gmail.com
> >
> > wrote:
> >
> > >
> > >
> > > On Tue, Aug 30, 2016 at 11:50 AM, Ellison Anne Williams <
> > > eawilliams@apache.org> wrote:
> > >
> > >> Hi,
> > >>
> > >> Given that it's generally a mess to put website updates through the PR
> > >> system (due to the large number of auxiliary files changed - in the
> > >> hundreds...), I have made several updates to the Apache Pirk website
> and
> > >> am
> > >> posting the list here so that folks can easily take a look and review.
> > I'm
> > >> more than happy to make edits to the pages today as needed. If there
> is
> > a
> > >> better way to do this, please let me know.
> > >>
> > >> - Making Releases page updated to reflect our current release
> > process:
> > >> http://pirk.incubator.apache.org/releasing
> > >> <http://pirk.incubator.apache.org/releasing>
> > >>
> > >
> > > You may not want to hardcode orgapachepirk-1001 here, it could be
> > > different for each staging Release Candidate - lets call it
> > > orgapachepirk-xxxx instead.
> > >
> > > Under the Section Rollback Release:
> >
> > If the rollback needs to happen after release:prepare and before
> > release:perform, the steps are:
> >
> > 1. mvn -Psigned_release release:rollback
> > 2. mvn -Psigned_release release:clean
> > 3. git tag -d <tagname>
> >
> >
> > >
> > >> - Keys link fixed from this page: http://pirk.incubator.
> > >> apache.org/downloads/ (fixes PIRK-60)
> > >> - News bar updated to reflect the first release: http://pirk.
> > >> incubator.apache.org/ (as well as the corresponding 'News' page
> > >> http://pirk.incubator.apache.org/news
> > >> <http://pirk.incubator.apache.org/news>)
> > >> - Javadocs updated: http://pirk.incubator.apache.org/javadocs/
> > >> - How to Contribute page updated to reflect license and notice
> > checks:
> > >> http://pirk.incubator.apache.org/how_to_contribute
> > >> <http://pirk.incubator.apache.org/how_to_contribute>
> > >>
> > >> Thanks!
> > >>
> > >> Ellison Anne
> > >>
> > >
> > >
> >
>
Re: Website Updates - Please Review
Posted by Ellison Anne Williams <ea...@apache.org>.
I never actually used 'mvn -Psigned_release release:rollback' to to roll
back the release -- I used the alternate steps that you gave here:
https://lists.apache.org/thread.html/c8acce2a20e8e2671d85fd8504bb2c7c52ebb5159b955ec762754bc7@%3Cdev.pirk.apache.org%3E
On Tue, Aug 30, 2016 at 12:08 PM, Suneel Marthi <su...@gmail.com>
wrote:
> On Tue, Aug 30, 2016 at 12:05 PM, Suneel Marthi <su...@gmail.com>
> wrote:
>
> >
> >
> > On Tue, Aug 30, 2016 at 11:50 AM, Ellison Anne Williams <
> > eawilliams@apache.org> wrote:
> >
> >> Hi,
> >>
> >> Given that it's generally a mess to put website updates through the PR
> >> system (due to the large number of auxiliary files changed - in the
> >> hundreds...), I have made several updates to the Apache Pirk website and
> >> am
> >> posting the list here so that folks can easily take a look and review.
> I'm
> >> more than happy to make edits to the pages today as needed. If there is
> a
> >> better way to do this, please let me know.
> >>
> >> - Making Releases page updated to reflect our current release
> process:
> >> http://pirk.incubator.apache.org/releasing
> >> <http://pirk.incubator.apache.org/releasing>
> >>
> >
> > You may not want to hardcode orgapachepirk-1001 here, it could be
> > different for each staging Release Candidate - lets call it
> > orgapachepirk-xxxx instead.
> >
> > Under the Section Rollback Release:
>
> If the rollback needs to happen after release:prepare and before
> release:perform, the steps are:
>
> 1. mvn -Psigned_release release:rollback
> 2. mvn -Psigned_release release:clean
> 3. git tag -d <tagname>
>
>
> >
> >> - Keys link fixed from this page: http://pirk.incubator.
> >> apache.org/downloads/ (fixes PIRK-60)
> >> - News bar updated to reflect the first release: http://pirk.
> >> incubator.apache.org/ (as well as the corresponding 'News' page
> >> http://pirk.incubator.apache.org/news
> >> <http://pirk.incubator.apache.org/news>)
> >> - Javadocs updated: http://pirk.incubator.apache.org/javadocs/
> >> - How to Contribute page updated to reflect license and notice
> checks:
> >> http://pirk.incubator.apache.org/how_to_contribute
> >> <http://pirk.incubator.apache.org/how_to_contribute>
> >>
> >> Thanks!
> >>
> >> Ellison Anne
> >>
> >
> >
>
Re: Website Updates - Please Review
Posted by Suneel Marthi <su...@gmail.com>.
On Tue, Aug 30, 2016 at 12:05 PM, Suneel Marthi <su...@gmail.com>
wrote:
>
>
> On Tue, Aug 30, 2016 at 11:50 AM, Ellison Anne Williams <
> eawilliams@apache.org> wrote:
>
>> Hi,
>>
>> Given that it's generally a mess to put website updates through the PR
>> system (due to the large number of auxiliary files changed - in the
>> hundreds...), I have made several updates to the Apache Pirk website and
>> am
>> posting the list here so that folks can easily take a look and review. I'm
>> more than happy to make edits to the pages today as needed. If there is a
>> better way to do this, please let me know.
>>
>> - Making Releases page updated to reflect our current release process:
>> http://pirk.incubator.apache.org/releasing
>> <http://pirk.incubator.apache.org/releasing>
>>
>
> You may not want to hardcode orgapachepirk-1001 here, it could be
> different for each staging Release Candidate - lets call it
> orgapachepirk-xxxx instead.
>
> Under the Section Rollback Release:
If the rollback needs to happen after release:prepare and before
release:perform, the steps are:
1. mvn -Psigned_release release:rollback
2. mvn -Psigned_release release:clean
3. git tag -d <tagname>
>
>> - Keys link fixed from this page: http://pirk.incubator.
>> apache.org/downloads/ (fixes PIRK-60)
>> - News bar updated to reflect the first release: http://pirk.
>> incubator.apache.org/ (as well as the corresponding 'News' page
>> http://pirk.incubator.apache.org/news
>> <http://pirk.incubator.apache.org/news>)
>> - Javadocs updated: http://pirk.incubator.apache.org/javadocs/
>> - How to Contribute page updated to reflect license and notice checks:
>> http://pirk.incubator.apache.org/how_to_contribute
>> <http://pirk.incubator.apache.org/how_to_contribute>
>>
>> Thanks!
>>
>> Ellison Anne
>>
>
>
Re: Website Updates - Please Review
Posted by Suneel Marthi <su...@gmail.com>.
On Tue, Aug 30, 2016 at 11:50 AM, Ellison Anne Williams <
eawilliams@apache.org> wrote:
> Hi,
>
> Given that it's generally a mess to put website updates through the PR
> system (due to the large number of auxiliary files changed - in the
> hundreds...), I have made several updates to the Apache Pirk website and am
> posting the list here so that folks can easily take a look and review. I'm
> more than happy to make edits to the pages today as needed. If there is a
> better way to do this, please let me know.
>
> - Making Releases page updated to reflect our current release process:
> http://pirk.incubator.apache.org/releasing
> <http://pirk.incubator.apache.org/releasing>
>
You may not want to hardcode orgapachepirk-1001 here, it could be different
for each staging Release Candidate - lets call it orgapachepirk-xxxx
instead.
> - Keys link fixed from this page: http://pirk.incubator.
> apache.org/downloads/ (fixes PIRK-60)
> - News bar updated to reflect the first release: http://pirk.
> incubator.apache.org/ (as well as the corresponding 'News' page
> http://pirk.incubator.apache.org/news
> <http://pirk.incubator.apache.org/news>)
> - Javadocs updated: http://pirk.incubator.apache.org/javadocs/
> - How to Contribute page updated to reflect license and notice checks:
> http://pirk.incubator.apache.org/how_to_contribute
> <http://pirk.incubator.apache.org/how_to_contribute>
>
> Thanks!
>
> Ellison Anne
>
Re: Website Updates - Please Review
Posted by Suneel Marthi <su...@gmail.com>.
Never mind, i see that this has been taken care of.. sorry!!
On Tue, Aug 30, 2016 at 11:57 AM, Suneel Marthi <su...@gmail.com>
wrote:
> There's one step we missed and is still pending in the Release process -
> creating a 0.1.0 tag in github and checking in the 0.1.0 artifacts against
> this tag.
>
> @ellisonAnne ^^^
>
> On Tue, Aug 30, 2016 at 11:50 AM, Ellison Anne Williams <
> eawilliams@apache.org> wrote:
>
>> Hi,
>>
>> Given that it's generally a mess to put website updates through the PR
>> system (due to the large number of auxiliary files changed - in the
>> hundreds...), I have made several updates to the Apache Pirk website and
>> am
>> posting the list here so that folks can easily take a look and review. I'm
>> more than happy to make edits to the pages today as needed. If there is a
>> better way to do this, please let me know.
>>
>> - Making Releases page updated to reflect our current release process:
>> http://pirk.incubator.apache.org/releasing
>> <http://pirk.incubator.apache.org/releasing>
>> - Keys link fixed from this page: http://pirk.incubator.
>> apache.org/downloads/ (fixes PIRK-60)
>> - News bar updated to reflect the first release: http://pirk.
>> incubator.apache.org/ (as well as the corresponding 'News' page
>> http://pirk.incubator.apache.org/news
>> <http://pirk.incubator.apache.org/news>)
>> - Javadocs updated: http://pirk.incubator.apache.org/javadocs/
>> - How to Contribute page updated to reflect license and notice checks:
>> http://pirk.incubator.apache.org/how_to_contribute
>> <http://pirk.incubator.apache.org/how_to_contribute>
>>
>> Thanks!
>>
>> Ellison Anne
>>
>
>
Re: Website Updates - Please Review
Posted by Suneel Marthi <su...@gmail.com>.
There's one step we missed and is still pending in the Release process -
creating a 0.1.0 tag in github and checking in the 0.1.0 artifacts against
this tag.
@ellisonAnne ^^^
On Tue, Aug 30, 2016 at 11:50 AM, Ellison Anne Williams <
eawilliams@apache.org> wrote:
> Hi,
>
> Given that it's generally a mess to put website updates through the PR
> system (due to the large number of auxiliary files changed - in the
> hundreds...), I have made several updates to the Apache Pirk website and am
> posting the list here so that folks can easily take a look and review. I'm
> more than happy to make edits to the pages today as needed. If there is a
> better way to do this, please let me know.
>
> - Making Releases page updated to reflect our current release process:
> http://pirk.incubator.apache.org/releasing
> <http://pirk.incubator.apache.org/releasing>
> - Keys link fixed from this page: http://pirk.incubator.
> apache.org/downloads/ (fixes PIRK-60)
> - News bar updated to reflect the first release: http://pirk.
> incubator.apache.org/ (as well as the corresponding 'News' page
> http://pirk.incubator.apache.org/news
> <http://pirk.incubator.apache.org/news>)
> - Javadocs updated: http://pirk.incubator.apache.org/javadocs/
> - How to Contribute page updated to reflect license and notice checks:
> http://pirk.incubator.apache.org/how_to_contribute
> <http://pirk.incubator.apache.org/how_to_contribute>
>
> Thanks!
>
> Ellison Anne
>
Re: Website Updates - Please Review
Posted by Tim Ellison <t....@gmail.com>.
On 30/08/16 16:50, Ellison Anne Williams wrote:
> Hi,
>
> Given that it's generally a mess to put website updates through the PR
> system (due to the large number of auxiliary files changed - in the
> hundreds...), I have made several updates to the Apache Pirk website and am
> posting the list here so that folks can easily take a look and review. I'm
> more than happy to make edits to the pages today as needed. If there is a
> better way to do this, please let me know.
>
> - Making Releases page updated to reflect our current release process:
> http://pirk.incubator.apache.org/releasing
> <http://pirk.incubator.apache.org/releasing>
> - Keys link fixed from this page: http://pirk.incubator.
> apache.org/downloads/ (fixes PIRK-60)
> - News bar updated to reflect the first release: http://pirk.
> incubator.apache.org/ (as well as the corresponding 'News' page
> http://pirk.incubator.apache.org/news
> <http://pirk.incubator.apache.org/news>)
> - Javadocs updated: http://pirk.incubator.apache.org/javadocs/
> - How to Contribute page updated to reflect license and notice checks:
> http://pirk.incubator.apache.org/how_to_contribute
> <http://pirk.incubator.apache.org/how_to_contribute>
>
> Thanks!
>
> Ellison Anne
>
I took a quick scan of the new page(s) and they look good. I'll follow
through in more detail later.
Regards,
Tim