librelist archives

« back to archive

Future Shoes release process

Future Shoes release process

From:
Steve Klabnik
Date:
2012-01-05 @ 21:49
Hey everyone! jrgifford mentioned this in another thread:

> Whats the "procedure" for a release? (probably should move to another thread...)

And I agree. It's been a while since we examined how things work. Now
that we've got some new contributors (<3 <3 <3 you all), we should
talk about this.

The current process is "there isn't really a process." A while back, I
moved development off of master and onto 'develop,' because I thought
git-flow was the shit. While it's not bad, I think it's pretty obvious
in our current state that it's a bit much. master hasn't been touched
in forever.

I _don't_ want to introduce a bunch of process. That's silly. However,
now that we're getting some commits, I'd like to release more often.
It'll help with morale, it'll help getting bugfixes out, it'll help
change the perception that the project is 'dead.'

I'd like to move to releasing once a quarter. What do you think?

I'd be in favor of cutting a release of whatever is on develop right
now, so we can start fresh. What do you think?

Re: [shoes] Future Shoes release process

From:
James Gifford
Date:
2012-01-05 @ 21:54
On Thu, Jan 5, 2012 at 4:49 PM, Steve Klabnik <steve@steveklabnik.com> wrote:
> Hey everyone! jrgifford mentioned this in another thread:
>
>> Whats the "procedure" for a release? (probably should move to another 
thread...)
>
> And I agree. It's been a while since we examined how things work. Now
> that we've got some new contributors (<3 <3 <3 you all), we should
> talk about this.
>
> The current process is "there isn't really a process." A while back, I
> moved development off of master and onto 'develop,' because I thought
> git-flow was the shit. While it's not bad, I think it's pretty obvious
> in our current state that it's a bit much. master hasn't been touched
> in forever.
>
> I _don't_ want to introduce a bunch of process. That's silly. However,
> now that we're getting some commits, I'd like to release more often.
> It'll help with morale, it'll help getting bugfixes out, it'll help
> change the perception that the project is 'dead.'

Agreed, keep it simple. Was just curious as to if there was anything
other than waking up and saying "lets release". ;)

> I'd like to move to releasing once a quarter. What do you think?

Once a quarter sounds good, gives us a goal.

> I'd be in favor of cutting a release of whatever is on develop right
> now, so we can start fresh. What do you think?

Sounds good, develop is pretty stable right now.

Re: [shoes] Future Shoes release process

From:
serialhex
Date:
2012-01-05 @ 22:42
On Thu, Jan 5, 2012 at 4:54 PM, James Gifford <james@jamesrgifford.com>wrote:

> > I'd like to move to releasing once a quarter. What do you think?
>
> Once a quarter sounds good, gives us a goal.
>

i like once a quarter, as long as it's something good!  i dont like the
idea of forced releases.  but yes +1 quarterly releases!!
hex


-- 
*  my blog is cooler than yours: http://serialhex.github.com
*  The wise man said: "Never argue with an idiot. They bring you down to
their level and beat you with experience."
*  As a programmer, it is your job to put yourself out of business. What
you do today can be automated tomorrow. ~Doug McIlroy
No snowflake in an avalanche ever feels responsible.
---
CFO: “What happens if we train people and they leave?”
CTO: “What if we don’t and they stay?”

Re: [shoes] Future Shoes release process

From:
Tobias Pfeiffer
Date:
2012-01-06 @ 11:24
On 01/05/2012 11:42 PM, serialhex wrote:
> On Thu, Jan 5, 2012 at 4:54 PM, James Gifford <james@jamesrgifford.com 
> <mailto:james@jamesrgifford.com>> wrote:
>
>     > I'd like to move to releasing once a quarter. What do you think?
>
>     Once a quarter sounds good, gives us a goal.
>
>
> i like once a quarter, as long as it's something good!  i dont like 
> the idea of forced releases.  but yes +1 quarterly releases!!
> hex
>
I agree that I don't like forced releases. I would say ~quarterly, but 
with maybe some features/bugs assigned a mile stone for a certain 
release and the release only happens of the associated features/bugs are 
closed. I believe this may also increase motivation to work on certain 
features/bugs.

What do you guys think?

Re: [shoes] Future Shoes release process

From:
Peter Fitzgibbons
Date:
2012-01-06 @ 15:31
I agree with quarterly.  Keep the scheudle "consistent".  Meaning, if we
dont' have a release at Q1 but we have code to release at Q1+3wk, then it
waits until true Q2.    So maybe there is no "July" release, yet the
consumer can expect that the next possible release would be Oct.

Thougths?
Peter Fitzgibbons
Email: peter.fitzgibbons@gmail.com
IM GTalk: peter.fitzgibbons
IM AOL: peter.fitzgibbons@gmail.com

Re: [shoes] Future Shoes release process

From:
Wayne Brisette
Date:
2012-01-06 @ 15:57
I'm going to throw my services out here for future Shoes releases (as long as I 
have time)... 

I am a technical writer, and while I love to dabble in scripting, it is writing 
documentation that pays the bills. If anybody needs or wants help in documenting 
anything, let me know. 

Wayne

Re: [shoes] Future Shoes release process

From:
Steve Klabnik
Date:
2012-01-06 @ 16:11
> I am a technical writer, and while I love to dabble in scripting, it is
> writing documentation that pays the bills. If anybody needs or wants help in
> documenting anything, let me know.

Soooooo this would be excellent. How can I help you help me with this?
Documentation is one of our biggest problems, actually.

Re: [shoes] Future Shoes release process

From:
Wayne Brisette
Date:
2012-01-06 @ 16:25
Steve:

I guess the first thing would be for us to determine where the major holes are, 
then start working on those. 

Wayne


----- Original Message ----
From: Steve Klabnik <steve@steveklabnik.com>
To: shoes@librelist.com
Sent: Fri, January 6, 2012 10:11:35 AM
Subject: Re: [shoes] Future Shoes release process

> I am a technical writer, and while I love to dabble in scripting, it is
> writing documentation that pays the bills. If anybody needs or wants help in
> documenting anything, let me know.

Soooooo this would be excellent. How can I help you help me with this?
Documentation is one of our biggest problems, actually.

Re: [shoes] Future Shoes release process

From:
James Gifford
Date:
2012-01-07 @ 02:12
Alright, back on the future release process.

About a month or so ago, Steve asked me to make something approaching
a "shoes test app" that does pretty much everything in the book of
shoes - however, it's far from being "ready".


Its as close as we have right now to a test suite, so should I just
commit it in its current state into the repo, and then have the
community build on it as part of the next release so we can make sure
we're "on the right track" come release day?

https://gist.github.com/1502049 (gist of that app)

Re: [shoes] Future Shoes release process

From:
Tobias Pfeiffer
Date:
2012-01-07 @ 08:40
Cool stuff!

yeah either the main shoes repo or its own repository (maybe a repo full 
of shoes examples?) and I think that would be a good solution.

Which reminds me of the fact that I think, that the url stuff in shoes 
still leads to a segfault :-/

Tobi

On 01/07/2012 03:12 AM, James Gifford wrote:
> Alright, back on the future release process.
>
> About a month or so ago, Steve asked me to make something approaching
> a "shoes test app" that does pretty much everything in the book of
> shoes - however, it's far from being "ready".
>
>
> Its as close as we have right now to a test suite, so should I just
> commit it in its current state into the repo, and then have the
> community build on it as part of the next release so we can make sure
> we're "on the right track" come release day?
>
> https://gist.github.com/1502049 (gist of that app)

Re: [shoes] Future Shoes release process

From:
Steve Klabnik
Date:
2012-01-07 @ 17:23
> Which reminds me of the fact that I think, that the url stuff in shoes
> still leads to a segfault :-/

Yeah. I started looking into it the other day, and got sidetracked by
some yaks that needed shaved. I might check that bug out today, if
not, then later this week.