Re: Past and preview License List releases (was: 3.1 release)

On Thu, Apr 05, 2018 at 03:04:05PM -0400, Brad Edmondson wrote: > I'm in favor of solving this (making html available for old versions > of the license list). I think it will help with adoption too, > especially as we move back to a more frequent release cadence. > > Perhaps add to the errata

Re: Past and preview License List releases (was: 3.1 release)

I'm in favor of solving this (making html available for old versions of the license list). I think it will help with adoption too, especially as we move back to a more frequent release cadence. Perhaps add to the errata issue? Or file a separate issue? -- Brad Edmondson, *Esq.* 512-673-8782 |

RE: Past and current License List releases (was: 3.1 release)

t; > Subject: Past and current License List releases (was: 3.1 release) > > On Mon, Mar 26, 2018 at 06:10:06AM -0700, Mark D. Baushke wrote: > > An alternative would be to use an ISO 8601 to express time. > > See https://en.wikipedia.org/wiki/ISO_8601 > > > > Version:

Past and current License List releases (was: 3.1 release)

On Mon, Mar 26, 2018 at 06:10:06AM -0700, Mark D. Baushke wrote: > An alternative would be to use an ISO 8601 to express time. > See https://en.wikipedia.org/wiki/ISO_8601 > > Version: 3.0 published on 2017-12-28 > > Version: 3.0 of 2017-12-28 +1 to using ISO dates. It would also be nice to be

Re: 3.1 release

Alexios makes a good point. An alternative would be to use an ISO 8601 to express time. See https://en.wikipedia.org/wiki/ISO_8601 Version: 3.0 published on 2017-12-28 Version: 3.0 of 2017-12-28 I will also note that if you do no like the International Standard Organization's view of time, you

RE: 3.1 release

Thanks Phillippe - > So may be one small thing that would go a very long way would be to: > > 1. create a page that has links to the older versions of the LL page 2. link > this "archives" page from the current LL version 3. link the previous version > too 4. as a bonus possibly link the

Re: 3.1 release

Gary, On Fri, Mar 23, 2018 at 3:22 PM, wrote: > It turns out we do maintain archived license lists, it just isn't very > well documented or publicized. > > There are also some formatting issues since older versions reference > some content which either isn't included in

Past and preview License List releases (was: 3.1 release)

On Fri, Mar 23, 2018 at 12:14:03PM -0700, Philippe Ombredanne wrote: > We are pushing new versions of the license lists but we are NOT > keeping online the previous versions. They are only in git repos. > I think it would help a lot adopters to have all the versions (at > least starting with 2.6

Re: 3.1 release

On Thu, Mar 22, 2018 at 12:22 PM, J Lovejoy <opensou...@jilayne.com> wrote: > I’m trying to get things nailed down for Gary to do the 3.1 release by end > of next week. > A few outstanding things that could go either way (resolved now via email > and included / or pushed to 3.2)

Re: 3.1 release

On Fri, Mar 23, 2018 at 02:28:57PM -0400, Steve Winslow wrote: > Apologies for any confusion from submitting as a separate PR, I'm > not sure how to modify or add commits to the existing PR at #551... You can stack your commits on top of the original PR's branch and then set that branch as the

Re: 3.1 release

test text file and add it so that this will pass. > > Thanks, > Steve > > On Thu, Mar 22, 2018 at 3:22 PM, J Lovejoy <opensou...@jilayne.com> wrote: > >> Hi all, >> >> I’m trying to get things nailed down for Gary to do the 3.1 release by >> end of

Re: 3.1 release

sou...@jilayne.com> wrote: > Hi all, > > I’m trying to get things nailed down for Gary to do the 3.1 release by end > of next week. > A few outstanding things that could go either way (resolved now via email > and included / or pushed to 3.2) - can I please get some input on these

3.1 release

Hi all, I’m trying to get things nailed down for Gary to do the 3.1 release by end of next week. A few outstanding things that could go either way (resolved now via email and included / or pushed to 3.2) - can I please get some input on these: https://github.com/spdx/license-list-XML/pull/551