You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwhisk.apache.org by David P Grove <gr...@us.ibm.com> on 2019/04/23 20:48:03 UTC
flatten structure of release directory
I would like to flatten out our release directory structure so that the
most recent version of each artifact is simply available in our top-level
release directory.
For unified releases, we would create a subdirectory (eg 19.05) and
replicate the specific individual components in that sub-directory (so it
is easy to manage the life-cycle of unified releases vs. individual
components).
This is consistent with how at least a couple other projects manager their
release directory (see conversation about release dir structures
intermingled with the IPMC release voting at [1]).
Lazy consensus, I'll wait 36 hours and then start reorganizing things and
submitting PRs to update the release-manager scripts. There will be a
window where we have some duplication of old & new structure while the
downloads page is being updated and scripts changed.
thanks,
--dave
[1]
https://lists.apache.org/thread.html/328826d8d7a85be797211f05d40dd1c2d40b53546bca4678f0e741c3@%3Cgeneral.incubator.apache.org%3E
Re: flatten structure of release directory
Posted by Dominic Kim <st...@gmail.com>.
+1
It will reduce the number of clicks to get a specific release.
Best regards
Dominic
2019년 4월 24일 (수) 오전 7:27, Carlos Santana <cs...@gmail.com>님이 작성:
> +1
>
> - Carlos Santana
> @csantanapr
>
> > On Apr 23, 2019, at 4:48 PM, David P Grove <gr...@us.ibm.com> wrote:
> >
> >
> >
> > I would like to flatten out our release directory structure so that the
> > most recent version of each artifact is simply available in our top-level
> > release directory.
> >
> > For unified releases, we would create a subdirectory (eg 19.05) and
> > replicate the specific individual components in that sub-directory (so it
> > is easy to manage the life-cycle of unified releases vs. individual
> > components).
> >
> > This is consistent with how at least a couple other projects manager
> their
> > release directory (see conversation about release dir structures
> > intermingled with the IPMC release voting at [1]).
> >
> > Lazy consensus, I'll wait 36 hours and then start reorganizing things and
> > submitting PRs to update the release-manager scripts. There will be a
> > window where we have some duplication of old & new structure while the
> > downloads page is being updated and scripts changed.
> >
> > thanks,
> >
> > --dave
> >
> > [1]
> >
> https://lists.apache.org/thread.html/328826d8d7a85be797211f05d40dd1c2d40b53546bca4678f0e741c3@%3Cgeneral.incubator.apache.org%3E
>
Re: flatten structure of release directory
Posted by Carlos Santana <cs...@gmail.com>.
+1
- Carlos Santana
@csantanapr
> On Apr 23, 2019, at 4:48 PM, David P Grove <gr...@us.ibm.com> wrote:
>
>
>
> I would like to flatten out our release directory structure so that the
> most recent version of each artifact is simply available in our top-level
> release directory.
>
> For unified releases, we would create a subdirectory (eg 19.05) and
> replicate the specific individual components in that sub-directory (so it
> is easy to manage the life-cycle of unified releases vs. individual
> components).
>
> This is consistent with how at least a couple other projects manager their
> release directory (see conversation about release dir structures
> intermingled with the IPMC release voting at [1]).
>
> Lazy consensus, I'll wait 36 hours and then start reorganizing things and
> submitting PRs to update the release-manager scripts. There will be a
> window where we have some duplication of old & new structure while the
> downloads page is being updated and scripts changed.
>
> thanks,
>
> --dave
>
> [1]
> https://lists.apache.org/thread.html/328826d8d7a85be797211f05d40dd1c2d40b53546bca4678f0e741c3@%3Cgeneral.incubator.apache.org%3E