New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New release ? #525

Open
ghost opened this Issue Mar 29, 2017 · 15 comments

Comments

Projects
None yet
3 participants
@ghost

ghost commented Mar 29, 2017

The last release was 2 years ago. Are there any thoughts of snapping a release tag on a commit and let some new code hit the distros ?

@Minoru

This comment has been minimized.

Show comment
Hide comment
@Minoru

Minoru Mar 29, 2017

Collaborator

Oh, there are thoughts for sure, but:

  • I don't want to create a tag without doing a release on newsbeuter.org because it'll create confusion in a number of ways; most importantly it'll mean we have a new release but search engines will still give users old docs.

  • newsbeuter.org is managed by @akrennmair who haven't been responding to my emails for nine months now. (I even emailed his work address; no luck.) Noone else has access to the domain as far as I know.

  • I really, really don't want to make a fork. It's quite a chunk of work, and doing it while the original author is still alive, well, and drinking beer seems premature.

  • I got a job a few months ago and life's still a bit hectic. I don't have energy for upheavals right now. (Though it was already running low even before the job, because working on Newsbeuter without knowing if we'll release anything ever turned out to be quite demotivating.)

So there we are.

Collaborator

Minoru commented Mar 29, 2017

Oh, there are thoughts for sure, but:

  • I don't want to create a tag without doing a release on newsbeuter.org because it'll create confusion in a number of ways; most importantly it'll mean we have a new release but search engines will still give users old docs.

  • newsbeuter.org is managed by @akrennmair who haven't been responding to my emails for nine months now. (I even emailed his work address; no luck.) Noone else has access to the domain as far as I know.

  • I really, really don't want to make a fork. It's quite a chunk of work, and doing it while the original author is still alive, well, and drinking beer seems premature.

  • I got a job a few months ago and life's still a bit hectic. I don't have energy for upheavals right now. (Though it was already running low even before the job, because working on Newsbeuter without knowing if we'll release anything ever turned out to be quite demotivating.)

So there we are.

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Mar 30, 2017

You could just mention all this in the release notes and just fork the documentation and put it up on a githup page.

ghost commented Mar 30, 2017

You could just mention all this in the release notes and just fork the documentation and put it up on a githup page.

@Minoru

This comment has been minimized.

Show comment
Hide comment
@Minoru

Minoru Mar 30, 2017

Collaborator

newsbeuter.org has been around for a decade and is linked from all over the Internet (and even from our own --version). GitHub page will take ages to overtake it; and by the time it does, I hope to finally prod Andreas into either transferring the domain or becoming more involved.

Collaborator

Minoru commented Mar 30, 2017

newsbeuter.org has been around for a decade and is linked from all over the Internet (and even from our own --version). GitHub page will take ages to overtake it; and by the time it does, I hope to finally prod Andreas into either transferring the domain or becoming more involved.

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Mar 30, 2017

Does it really need to ? You could just employ this a temporary solution which may or may not become permanent. It's been 9 months. Why do we have so many cases of "what happens when you get hit by a bus" in the open source community when you can't push a new release forward because of this.

ghost commented Mar 30, 2017

Does it really need to ? You could just employ this a temporary solution which may or may not become permanent. It's been 9 months. Why do we have so many cases of "what happens when you get hit by a bus" in the open source community when you can't push a new release forward because of this.

@Minoru

This comment has been minimized.

Show comment
Hide comment
@Minoru

Minoru Mar 30, 2017

Collaborator

Does it really need to ?

Yes, otherwise the GitHub page will be useless (users won't see it).

You could just employ this a temporary solution which may or may not become permanent.

I don't see a tag and docs on some unknown site as a solution. To me, a solution will mean that either newsbeuter.org is active again, or a fork occurs and new project does releases at its own home.

Collaborator

Minoru commented Mar 30, 2017

Does it really need to ?

Yes, otherwise the GitHub page will be useless (users won't see it).

You could just employ this a temporary solution which may or may not become permanent.

I don't see a tag and docs on some unknown site as a solution. To me, a solution will mean that either newsbeuter.org is active again, or a fork occurs and new project does releases at its own home.

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Mar 30, 2017

I think I understand your point of view. I have nothing more to add, thanks for your responses.

ghost commented Mar 30, 2017

I think I understand your point of view. I have nothing more to add, thanks for your responses.

@fornwall

This comment has been minimized.

Show comment
Hide comment
@fornwall

fornwall Jun 12, 2017

Any progress on getting out a release? Is master considered stable enough for a distribution to pick up?

fornwall commented Jun 12, 2017

Any progress on getting out a release? Is master considered stable enough for a distribution to pick up?

@Minoru

This comment has been minimized.

Show comment
Hide comment
@Minoru

Minoru Jun 12, 2017

Collaborator
Collaborator

Minoru commented Jun 12, 2017

@Minoru

This comment has been minimized.

Show comment
Hide comment
@Minoru

Minoru Jun 15, 2017

Collaborator

Is master considered stable enough for a distribution to pick up?

Well, nothing critical has been reported against it, so I guess it is.

I have to take that back. 2.10 milestone shows that we have two more bugs to fix before the release.

Collaborator

Minoru commented Jun 15, 2017

Is master considered stable enough for a distribution to pick up?

Well, nothing critical has been reported against it, so I guess it is.

I have to take that back. 2.10 milestone shows that we have two more bugs to fix before the release.

@Minoru

This comment has been minimized.

Show comment
Hide comment
@Minoru

Minoru Aug 22, 2017

Collaborator

Since my last comment, two things changed:

  • I got a semblance of peace with my dayjob. Now I know how little energy and time I have, and can plan around that properly. I am more ready for upheavals now :)

  • Due to #591, I am becoming less perfectionist about the solutions I should employ. Specifically, I am at the brink of doing GitHub releases and posting docs somewhere other than newsbeuter.org. I am not actively working on this yet, but at least I no longer consider this a non-solution.

Collaborator

Minoru commented Aug 22, 2017

Since my last comment, two things changed:

  • I got a semblance of peace with my dayjob. Now I know how little energy and time I have, and can plan around that properly. I am more ready for upheavals now :)

  • Due to #591, I am becoming less perfectionist about the solutions I should employ. Specifically, I am at the brink of doing GitHub releases and posting docs somewhere other than newsbeuter.org. I am not actively working on this yet, but at least I no longer consider this a non-solution.

@klartext

This comment has been minimized.

Show comment
Hide comment
@klartext

klartext Aug 22, 2017

@Minoru
If you don't want to call a new release 2.10, because of the milestones,
just call it 2.9.a 2.9.b or something similar.
It's just a oneliner for the tagging and a push, and you make many people happy.

Regarding the security-issue: just disable bookmarking, until there is a valid solution,
which might be called 2.9.c or something like that.

klartext commented Aug 22, 2017

@Minoru
If you don't want to call a new release 2.10, because of the milestones,
just call it 2.9.a 2.9.b or something similar.
It's just a oneliner for the tagging and a push, and you make many people happy.

Regarding the security-issue: just disable bookmarking, until there is a valid solution,
which might be called 2.9.c or something like that.

@klartext

This comment has been minimized.

Show comment
Hide comment
@klartext

klartext Aug 23, 2017

@Minoru: I have two different newsbeuters running here.
The one is 2.10-d1c1, the other is 2.10-e0f9.
How can that be?

klartext commented Aug 23, 2017

@Minoru: I have two different newsbeuters running here.
The one is 2.10-d1c1, the other is 2.10-e0f9.
How can that be?

@Minoru

This comment has been minimized.

Show comment
Hide comment
@Minoru

Minoru Aug 23, 2017

Collaborator
Collaborator

Minoru commented Aug 23, 2017

@klartext

This comment has been minimized.

Show comment
Hide comment
@klartext

klartext Aug 23, 2017

I'm confused now.
Did you read my answer from yesterday?

klartext commented Aug 23, 2017

I'm confused now.
Did you read my answer from yesterday?

@Minoru

This comment has been minimized.

Show comment
Hide comment
@Minoru

Minoru Aug 23, 2017

Collaborator
Collaborator

Minoru commented Aug 23, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment